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

Annotations already establish the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds two genuine behavioral traits beyond the annotations: output is 'bounded' and 'citation-preserving', which tells the agent the return is size-limited and includes provenance. It does not explain what bounds apply or how citations are formatted.

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?

A single front-loaded sentence with no redundant clauses. The trailing phrase 'suitable for grounding AI responses' is mildly marketing-flavored but does carry the intended use case, so it roughly earns its place.

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 3-parameter read tool with annotations covering safety and a fully documented schema, the description is adequate but thin. With no output schema present, the description should give more shape to the returned 'bundle' (what it contains, how depth/maxRelated affect it) than a single adjective-laden phrase.

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?

Schema description coverage is 100% and each parameter carries its own inline description ('Canonical concept slug', '0 or 1 hop', 'Maximum neighbors'), so the schema already does the parameter work. The description adds no syntax or format detail beyond that, matching the baseline for fully documented schemas.

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 ('Retrieve') and resource ('semantic context bundle') with two distinguishing attributes ('bounded', 'citation-preserving'). It is clear what the tool returns, but it never names or differentiates itself from the siblings get_concept, get_relationships, or search_concepts, so an agent must infer why 'context bundle' differs from a plain concept fetch.

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?

Usage is only implied by 'suitable for grounding AI responses', which hints at the scenario without stating when to prefer this over get_concept or search_concepts. No exclusions or preconditions (e.g., that id must be a known concept slug) are given.

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