property_investment_analysis

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the analysis outputs, it doesn't describe what the tool actually does behaviorally - whether it performs calculations, generates reports, makes recommendations, or requires specific permissions. For a complex financial analysis tool with no annotation coverage, this is a significant gap in transparency.

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 appropriately concise - a single sentence that efficiently communicates the tool's scope and outputs. It's front-loaded with the main purpose and doesn't contain unnecessary verbiage. However, given the complexity of the tool, this brevity comes at the cost of completeness.

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?

For a complex financial analysis tool with no annotations, no output schema, and a sophisticated input structure, the description is insufficient. It doesn't explain what the analysis entails, what format the results take, what assumptions are made in calculations, or how to interpret the outputs. The single sentence description leaves too many questions unanswered for effective tool selection and use.

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?

With 0% schema description coverage and a complex nested parameter structure (1 top-level parameter with 8+ sub-properties), the description provides no information about required inputs. It doesn't mention that a 'property' object with specific financial and operational metrics is needed, nor does it explain the relationship between parameters like 'acquisitionPrice' and 'currentMarketValue' for ROI calculations.

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 tool's purpose as performing 'comprehensive property investment performance analysis' with specific outputs (ROI, cap rates, cash flow projections). It distinguishes itself from sibling tools like 'rental_calculate_cap_rate' or 'rental_project_cash_flow' by offering a more comprehensive analysis rather than single calculations. However, it doesn't explicitly differentiate from 'create_rental_property_analysis' which might be similar.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools performing related analyses (e.g., 'rental_calculate_cap_rate', 'rental_project_cash_flow', 'create_rental_property_analysis'), there's no indication of when this comprehensive analysis is preferred over more focused tools or what specific scenarios warrant its use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.