get_taxonomies

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

Discloses read-only nature, no side-effects, and no authentication required. While no annotations exist, the description covers key behavioral traits effectively. Could add more about return format details but not necessary given simplicity.

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?

Extremely concise: three sentences covering purpose, behavior, and usage guidance. No superfluous words, front-loaded with key 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?

Given low complexity, one required parameter, and no output schema needed, the description fully covers all necessary information: what it does, what it returns, when to use it, and its safety profile.

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% with enums documented. Description adds context by explaining the purpose of the parameter (taxonomy type) and ties it to real-world usage (locations/industries).

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 uses a specific verb ('Retrieves') and resource ('available filter slugs for locations or industries'), and explicitly distinguishes from the sibling 'get_jobs' by stating usage context.

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?

Clearly states when to use this tool: 'Use this tool before get_jobs when you need to verify if a specific region or category slug exists.' Provides explicit guidance on prerequisites and context.

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