get_occupancy_summary_report

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

No behavioral traits disclosed beyond the basic summary generation. No annotations provided, so description should cover read-only nature or performance implications, but it does not. Only mentions ID format which is parameter semantics.

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?

Two sentences plus a column list. No redundancy, front-loaded with purpose and critical usage note. 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?

Covers main purpose and parameter constraints but omits explanation of output structure (e.g., grouped by property) and the role of the nested properties object. Lacks guidance on how the filters interact or what the required as_of_date implies.

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. Description adds value by emphasizing numeric string requirement for IDs and listing common columns with clarifications (e.g., use 'occupied' for count). Adds meaning beyond schema.

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?

Clearly states verb 'Generates a summary' and resource 'property occupancy' with specific metrics (units, occupied, vacancy rates). Distincts from sibling reports like get_leasing_summary_report or get_unit_vacancy_detail_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 explicit instruction that IDs must be numeric strings and directs users to directory reports for ID lookup. Lacks explicit when-not to use or comparison with siblings, but the important note is highly actionable.

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