get_leasing_funnel_performance_report

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as side effects, rate limits, pagination, or output format. The only additional behavioral info is the ID format requirement, but that is parameter-level, not behavioral.

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 contains two sentences: one stating the purpose and one providing critical usage guidance. It is concise, front-loaded, and every sentence adds value.

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 (7 parameters, nested objects, no output schema), the description is minimal. It does not explain the report contents, result interpretation, or relationship to other reports. It meets the minimum for agent usage but leaves significant gaps.

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 only 14%, but the description repeats the key ID format requirement already present in the schema. It does not add new meaning for other parameters like date_from, date_to, or columns. The description is adequate but does not compensate for the low schema coverage.

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 'Returns leasing funnel performance report' with a specific verb and resource. The tool name is distinct among many sibling reports, and the description effectively distinguishes it by focusing on leasing funnel performance.

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 requires ID parameters to be numeric strings and directs users to use directory reports for ID lookups. This provides clear when-to-use and when-not-to-use guidance, referencing sibling tools like get_owner_directory_report.

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