list_glossary_terms

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

No annotations provided, so description must fully convey behavior. It mentions pagination and filtering but lacks details on defaults, such as whether deleted terms are excluded by default, or how filtering by 'glossary' works (name vs ID). No mention of response structure or rate limits.

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?

One sentence, concise but lacks necessary detail for a tool with 5 parameters and no schema descriptions. Could be improved by front-loading key info without adding much length.

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 5 parameters, no output schema, and no annotations, the description is insufficient. Does not inform about response format, pagination behavior (e.g., total count, next page), or filtering constraints.

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 description should explain parameters. However, it only vaguely mentions 'pagination and filtering' without describing specific parameters like 'fields' (comma-separated? JSON?), 'glossary' (filter by name? ID?), or 'include_deleted' (what counts as deleted?).

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?

Description clearly states it lists glossary terms with pagination and filtering. The verb 'list' matches the resource 'glossary_terms', distinguishing it from 'get_glossary_term' (singular) and 'list_glossaries' (different resource).

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 guidance on when to use this tool vs alternatives like 'get_glossary_term' or 'search_entities'. No mention of prerequisites or context for using pagination/filtering parameters.

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