get_owner_leasing_report

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

No annotations are provided, so the description must carry the full burden. It describes the report's purpose and the ID format requirement but does not disclose whether the operation is read-only, any side effects, or the exact contents of the report. The description adds value but misses some behavioral context.

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 exactly two sentences: one for purpose and one for critical usage guidelines. It is front-loaded, concise, and contains no filler. Every sentence earns its place.

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 7 parameters (nested object), 2 required, and no output schema, the description covers the core purpose and a key constraint. However, it does not explain the output structure or any defaults beyond what the schema already provides, leaving some gaps in completeness.

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 description coverage is 100%, so the schema documents all parameters. The description adds the critical instruction on numeric string IDs and the need to use directory reports, which goes beyond the schema. It enriches the semantic understanding of parameters.

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 provides a leasing report tailored for property owners, with leasing activity within a date range. This specific verb+resource combination distinguishes it from 45 sibling reports (e.g., get_leasing_summary_report or get_leasing_funnel_performance_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?

The description explicitly mandates that all ID parameters must be numeric strings (not names) and instructs users to use directory reports to look up IDs first. This provides clear, actionable guidance for correct usage but does not explicitly compare with sibling leasing reports.

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