get_arrest_data

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

No annotations provided, so description carries full burden. Explains parameter dependencies (e.g., aggregate only for counts). Could mention data freshness or read-only nature, but overall transparent about tool behavior.

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?

Well-structured with clear 'Args' section. Each sentence adds value without redundancy. Efficiently conveys necessary information.

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 all parameters with dependencies explained. Includes cross-reference for offense codes. Output schema exists so return values need not be described. Complete for a 9-parameter tool.

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 no descriptions (0% coverage), but the description provides extensive semantics for all 9 parameters, including examples, defaults, constraints, and cross-references. Adds significant value beyond bare 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?

The description clearly states 'Get arrest statistics by offense, optionally broken down by demographics.' The verb 'get' and resource 'arrest statistics' are specific. Differentiates from sibling tools like get_crime_trends which focus on broader 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?

Provides detailed parameter instructions including examples for offense codes, required parameters for geographic levels, and points to get_reference_data for full offense list. Lacks explicit when-not-to-use or direct comparison to siblings, but sufficient for a complex tool.

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