Compact graph digest (token-cheap)

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds that it uses getNetworkTopology + getNetworkErrors, and lists the exact return shape, going beyond annotations.

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?

Four concise sentences, front-loaded with key purpose and behavior. Every sentence adds value: read-only, compress, return structure, underlying methods, comparison to siblings.

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?

Despite having output schema, description lists return keys. Covers use case, limitations, and relationship to other tools. Adequate for a tool with 6 optional parameters and no required fields.

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?

All 6 parameters have full schema coverage (100%). Description adds context like 'Hard ceiling on approximate output tokens' and 'Include top-3 grouped error keys. Off for purely structural turns.' Enhances understanding beyond schema.

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?

Clearly states 'compress a TD subtree into a structured digest' with a specific verb and resource. Distinguishes from siblings by referencing get_td_topology / snapshot_td_graph and noting it's cheaper for planning.

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?

Explicitly says 'Read-only' and 'no new bridge work. Cheaper than... for planning turns.' Provides clear context for when to use this tool over alternatives, with named sibling tools.

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