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 and delivers none of it. Nothing is said about read/write semantics, return shape, or scoping. The description adds zero information beyond the name.

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?

Two words is technically short, but this is under-specification rather than conciseness. There is no front-loaded statement of action or result because there is effectively no content.

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 tool with an undocumented parameter and no annotations or output schema, the description is completely inadequate. An agent cannot determine what 'anchors' are, what calling it returns, or how it differs from the other glossary endpoints.

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 single 'language' parameter has 0% schema description coverage and the description never mentions it. With no schema annotations and no compensating text, the agent cannot tell what the parameter controls or what values it accepts.

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 is the name restated with the underscore replaced by a space: 'Glossary anchors'. It names no verb and gives no indication of what the tool returns or does with anchors. Siblings like glossary, glossary_by_slug, and glossary_search are indistinguishable from this on the basis of the description.

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?

There is no guidance whatsoever on when to use this tool versus the sibling glossary tools. An agent has no basis for choosing it over glossary, glossary_by_slug, or glossary_search.

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