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

The annotations already define read-only and idempotent behavior; the description goes further by revealing human-editor provenance ('not generated'), clearly listing the pro tip and business-specific fields that are excluded, and providing a follow-up (citation_url). This shifts the behavioral boundary beyond what annotations encode.

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?

Three sentences: purpose and fields, editorial human origin, and a clear exclusion list with a redirect. No fluff; every sentence adds actionable information and the most important scoping info is forced to the front.

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 one parameter and an output schema, the description covers what is returned and what isn't, plus the source of slug and an alternative for missing content. The only gap is not referring by name to the obvious sibling 'get_concept_card', which would fully seve the disambiguation for an agent, but the citation_url guidance partially compensates.

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 has 100% description coverage for the single 'slug' parameter, stating it comes from search_concepts. The description's mention of 'by slug' is redundant with the schema. It does not add additional format, example examples, or edge-case info, so it's at the expected baseline for full 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 verb 'fetch', the resource ('one concept entry by slug'), and the expected output fields (title, category, tags, editor's summary). The explicit list of what is NOT returned distinguishes it from the sibling get_concept_card and makes the tool's scope 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?

It explains the intended use case (fetch public metadata and editor summary) and warns against expecting subscriber-only content, directing the caller to citation_url for those. However, it does not name the sibling tool get_concept_card or explicitly state conditions for choosing one over the other, leaving partential ambiguity.

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