Get detailed house project information including specifications, price, features, and company contacts.
Args: project_id: Project UUID from search_projects results
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only operation via 'Get' but does not explicitly confirm non-destructiveness, auth requirements, or rate limits. The verb suggests safety, but more explicit disclosure would be better.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: one sentence for purpose and one line for the parameter. It is front-loaded and contains no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that an output schema exists (as per context signals), the description appropriately focuses on input and general content. It lists what is included (specs, price, features, contacts) but could mention that it returns a single project object or handle error cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% coverage, and the description adds meaning by specifying that project_id is a UUID from search_projects results. This compensates for the schema's lack of description, though it could elaborate on format or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'detailed house project information', and lists specific contents (specifications, price, features, company contacts). It distinguishes itself from siblings like search_projects (which searches/finds projects) and get_company (company info).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states that project_id should come from search_projects results, providing clear context for its use. However, it does not mention when not to use this tool or explicitly compare with alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have overlapping purposes: search_companies, find_best_companies, smart_match, and contractor_recommendation all find contractors; get_company, company_portfolio, and company_deep_profile all return company details; calculate_cost and project_estimator both estimate costs. This makes it difficult for an agent to reliably choose the correct tool.
Tool names mix verb-first patterns (get_*, search_*, compare_*, calculate_*, export_*, find_*, request_*) with noun-first patterns (company_deep_profile, market_report, price_comparison, etc.). All names use snake_case, but the inconsistent verb/noun placement makes the set less predictable.
24 tools falls squarely in the 16-25 'feel heavy' range. While the server covers a broad domain (companies, projects, analytics, leads, estimation), the presence of many overlapping tools suggests the count could be consolidated without losing functionality.
The toolset covers the core domain well: searching companies and projects, retrieving full details, comparing entities, estimating costs, obtaining market analytics, and managing the lead lifecycle (request_quote -> get_lead_status). Minor gaps exist (e.g., no detailed per-review text, but that is explicitly stated as unavailable), but there are no dead ends for typical workflows.