get_expanded_homicide_data

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

No annotations exist, so description carries full behavior burden. It details data types (counts/totals), aggregation (yearly/monthly), date formats, and conditional parameter requirements. It does not explicitly state read-only or safety, but behavior is clear and non-destructive.

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: one introductory sentence followed by a structured Args list. Each parameter explanation is brief yet complete. No unnecessary words.

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 7 parameters, no annotations, and an output schema (not shown), the description covers all needed context: parameter semantics, conditional requirements, and data scope. No gaps for the agent to use the tool correctly.

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 has 0% description coverage, but the description's Args section provides thorough explanations for each of the 7 parameters, including required conditions, defaults, and formats (e.g., 'mm-yyyy' for dates, 'state' requirement). Fully compensates for schema gaps.

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 'Get Supplementary Homicide Report (SHR) data with expanded details on homicides including victim/offender demographics, weapons, and circumstances.' This is a specific verb+resource and differentiates from sibling tools like get_hate_crime_data or get_summarized_crime_data.

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?

Description explains parameter requirements (e.g., state required for level='state') and data_type options (counts vs totals). However, it does not explicitly state when to use this tool versus siblings, though context implies it for homicide-specific data.

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