list_districts

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

No annotations provided; description only notes it gives data from Google's Divisions API but does not disclose auth needs, rate limits, or behavior quirks. Limited transparency.

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?

Single sentence, no redundancy. Front-loaded with key information. Concise but could benefit from a slight structure improvement (e.g., bullet points for district types).

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 primary purpose and types of districts. Lacks output schema details and error handling. For a simple tool, it suffices; but given siblings, more context on integration might help.

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 0% (no param descriptions). The parameter 'address' is not elaborated on—no format, examples, or constraints. Despite the single parameter, description does not compensate for schema silence.

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 it lists districts/divisions (congressional, state-legislative, OCD-IDs) for an address. Differentiates from siblings like get_official_details and lookup_by_district by focusing on raw district 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?

No explicit guidance on when to use this tool versus siblings. The mention 'just the piece...' implies a specific use case but does not state conditions or alternatives.

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