calculate_rental_profitability

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

No annotations are provided, so the description must fully disclose behavior. It describes the output but misleadingly references parameters not in the schema, which undermines transparency about what inputs are actually used.

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 short but includes inaccurate information about inputs, making it not truly concise. Misleading content outweighs brevity.

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?

With 5 parameters and an output schema, the description should provide complete context. It fails to explain the input discrepancy and does not cover all aspects, leaving the agent misinformed.

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?

Schema coverage is 100%, so baseline is 3, but the description lists parameters (vacancy %, tax bracket) that are absent from the schema. This adds no value and creates confusion, reducing the score.

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 states it computes net rental profitability after taxes and charges, which is clear. However, it mentions inputs (vacancy %, tax bracket) that are not in the schema, and does not differentiate from sibling tools like calculate_rental_yield_net, causing confusion.

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?

Says 'Use for real estate investment analysis,' but provides no when-to-use vs. alternatives. The suggestion to see list_bundles is too vague to guide selection among many rental-related calculators.

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