Browse Vocabulary

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

Annotations already declare readOnly, non-destructive, and idempotent behavior. The description adds that it supports pagination, returns a list of concepts with code and label, and gives output structure. No contradictions.

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 headers (Args, Returns, When to use, Use for). Every sentence adds value, no redundancy. Front-loaded with the core purpose.

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?

Comprehensive for a tool with 5 parameters and sibling comparison. Explains input, output, usage guidance, and use cases. No output schema, but description provides clear output structure.

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 description coverage is 60% (3 of 5 parameters have descriptions). The description adds value for the undocumented 'limit' and 'offset' by listing defaults and purpose, and clearly explains optional parameters and language options.

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 'Browse concepts in a vocabulary with pagination support', specifying the verb 'browse' and resource 'concepts in a vocabulary'. Explicitly distinguishes from sibling 'search_in_vocabulary'.

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 'When to use this vs X' section, comparing with 'search_in_vocabulary' and stating that this is the preferred default for exploring a known ConceptScheme due to pagination support, while the alternative is for lightweight keyword lookups.

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