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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint false), so the remaining burden is explaining what a call yields. The description does that well by naming the three payload parts and the fact that each neighbor carries its relation. It stops short of saying anything about missing-id behavior or error semantics.

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?

Opens with the core fetch semantics and return shape, then layers usage routing; nearly every clause earns its place. The closing 'use search_concepts instead' slightly repeats the earlier 'use after search_concepts' framing, a minor redundancy rather than padding.

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?

There is no output schema, so describing return values is mandatory here and the description does it precisely. Combined with annotations covering safety, an agent has everything needed to decide to call it and what to expect afterward.

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?

With 100% schema description coverage and a single required parameter, the schema already defines the id format and gives an example slug. The description reinforces exact-match lookup, but adds no new syntax or constraint details beyond what is structured. Baseline 3 applies.

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?

States a specific verb+resource (fetch one concept by exact id) and immediately enumerates what comes back: full markdown body, metadata, and direct graph neighbors with their connecting relation. It is clearly distinguished from the sibling search_concepts, which returns the ids this tool consumes.

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?

Gives explicit entry conditions ('Use after search_concepts or when another note wiki-links an id') and an explicit exclusion with the alternative ('If you don't know the id, use search_concepts instead'). It also explains how to continue work ('the neighbors list tells you what to fetch next'), which no sibling tool description could supply.

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