property_performance_report

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

No annotations provided, so description carries full burden. It discloses that the tool combines 3 API calls in parallel and calculates specific metrics (days on market, total inquiries, deals by stage, activity breakdown). This provides good behavioral insight beyond basic purpose.

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?

Description is concise and well-structured. It uses bullet points and a clear example, making it easy to scan. No unnecessary sentences.

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?

Despite having no output schema, the description fully explains what the report contains (specific metrics, data sources, calculations). An agent can confidently understand what will be returned.

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?

Only one parameter (property_id) with 100% schema coverage. Description does not add extra semantics for the parameter beyond what the schema already provides ('Property ID to generate report for'). The description focuses on overall behavior, not parameter detail.

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?

Description clearly states the tool generates a performance report for a property, listing specific metrics (days on market, inquiries, pipeline breakdown, activity summary). It distinguishes from siblings like 'get_property' and 'search_deals' by being a composite report.

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?

Provides a concrete usage example ('How is the Friedrichstr property doing?'), making it clear when to invoke. Does not explicitly state when not to use or list alternatives, but the context is strong.

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