get-glossary-info

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly notes that the tool does not fetch glossary entries, which is a key behavioral constraint, and clarifies the exact metadata returned. While it does not discuss error handling or authentication, for a read-only metadata retrieval that is sufficient to meet most expectations.

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?

The description is two concise sentences, front-loaded with the core purpose and followed by a valuable scope clarification. Every word earns its place, with no repetition or filler.

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 simple single-parameter tool with no output schema or annotations, the description is complete enough: it states what it returns, what it does not return, and points to the correct sibling for entries. It could optionally mention error behavior or the relationship to 'list-glossaries', but the core context is well covered.

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?

The schema already fully describes the only parameter (glossaryId as a unique identifier string), so the description adds little beyond the schema. It uses 'Given an id' but doesn't elaborate on format, constraints, or behavior related to the parameter, which is acceptable given 100% schema coverage.

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 clearly states the tool's function with a specific verb ('get metadata') and resource ('glossary'), and explicitly lists the returned metadata (name, available dictionaries, creation time). It also distinguishes itself from sibling tool 'get-glossary-dictionary-entries' by stating what it does not do, making its purpose unmistakable.

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?

The description explicitly says when to use this tool (to get glossary metadata) and provides an alternative ('Use the get-glossary-dictionary-entries tool to fetch entries'), giving direct usage guidance and differentiating from a likely alternative.

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