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

With no annotations provided, the description carries the full burden. It discloses that the tool returns 'full definition and links,' which is helpful, but it does not mention error behavior, read-only nature explicitly, or any other side effects. This is minimal but not misleading.

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 a single sentence of 11 words, front-loading the core action ('Get a single glossary term') and adding useful detail about the return content. Every word earns its place, with no 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 getter with one parameter, no annotations, and no output schema, the description is largely sufficient. It tells the agent what the tool does and what is returned, but could benefit from explicit note about when to choose this over `list_glossary` or how missing slugs are handled. Still, it is complete for most use cases.

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 input schema has 100% coverage for the single parameter `slug`, with a description 'Glossary slug.' The tool description does not add additional meaning about the parameter, so it relies on the schema. No extra semantic context is provided.

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 retrieves a single glossary term, using the verb 'get' and specifying the resource. The word 'single' distinguishes it from the sibling `list_glossary` tool, making its purpose unambiguous.

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 implies usage for fetching one specific term but does not explicitly mention alternatives like `list_glossary` for retrieving multiple terms. There is no direct when-to-use guidance or exclusions, only implied context.

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