List Terms

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read operation, and 'with filters and pagination' hints at query behavior, but there is no mention of permissions, rate limits, pagination bounds, or filter syntax, leaving the safety profile to inference.

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?

A single, front-loaded sentence with zero wasted words. It is appropriately sized for a straightforward list operation.

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?

For a 5-parameter tool with no annotations and zero schema descriptions, the description is not complete enough. It fails to document the required vid or the sorts parameter, and provides no guidance on filter syntax or pagination limits, though the output schema covers return values.

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 0%, so the description must compensate. It mentions 'filters' and 'pagination' (mapping to filters, page_limit, page_offset) and implies vid via 'in a vocabulary', but omits the sorts parameter entirely and provides no syntax or format details for any parameter.

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?

States a specific verb ('List') and resource ('terms') scoped to a vocabulary, which distinguishes it from get_term (single term) and list_vocabularies (vocabularies). However, it does not explicitly name alternatives or clarify that it returns a paginated collection versus a single term.

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 when-to-use guidance, prerequisites, or alternatives are provided. The description only states what it does, leaving the agent to infer that this is for listing taxonomy terms within a known vocabulary.

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