rental_calculate_cap_rate

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. It only states the calculation action without any details on permissions, rate limits, side effects, or output format. This is inadequate for a tool with parameters and no output schema, as it leaves critical behavioral traits unspecified.

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 a single, efficient sentence with no wasted words, making it easy to parse. It is appropriately sized for a simple calculation tool, though this conciseness 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?

Given the tool's complexity (a financial calculation with 3 parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It does not provide enough context for an agent to understand how to use the tool effectively or interpret results.

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% description coverage, and the tool description does not explain the parameters at all. It fails to add meaning beyond the schema, such as clarifying what 'propertyId', 'propertyValue', and 'year' represent in the context of cap rate calculation, leaving parameters undocumented.

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 'Calculate capitalization rate for a property' clearly states the verb ('calculate') and resource ('capitalization rate for a property'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'rental_calculate_noi' or 'property_investment_analysis', which might involve similar calculations, so it falls short of a perfect score.

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, such as other financial calculation tools in the sibling list. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage based on the tool name alone.

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