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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the 15-record cap, that only `related_pages` edges exist today, that an unlinked page returns an empty group list rather than an error, that there is no pagination, ~10-minute caching, per-IP rate limiting, and retry-on-5xx behavior. This is unusually rich operational context.

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?

Front-loads the core behavior, then packs edge cases into tight clauses. Every sentence conveys a distinct constraint (cap, edge coverage, empty result, pagination, caching, rate limits) 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?

With an output schema present, return values need not be explained, and the description nonetheless covers result shape, cap, empty-case semantics, and operational limits. An agent has everything needed to call this correctly.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely new meaning: the accepted `record_id` forms (`page:` ID or permalink) and the `edge_type` default of 'all', which the schema does not state. It does not enumerate valid edge type values, which stays as a residual gap.

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 and scope: 'Traverse the ESG Hub knowledge graph one hop from a page and return every connected record grouped by edge type.' It explicitly distinguishes itself from get_esg_page, so an agent can tell the two apart without opening a schema.

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 sequencing ('use it after get_esg_page when you need neighbouring concepts') and names the alternative with its selecting condition ('to read a page's own content use get_esg_page'). Nothing is left to inference.

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