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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds meaningful context beyond them: it returns "dates, change classes, stored hashes and whether yours match," is "facts, not a verdict," is free with no account, and requires public non-personal inputs. That is genuinely useful disclosure for a check tool.

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?

The description is compact and front-loads the trigger ("Use this before connecting") ahead of mechanics and constraints. Every sentence carries weight, with only the param recap being arguably redundant against the 100%-covered schema.

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 six-parameter, no-required, no-output-schema tool, the description covers purpose, usage timing, return contents, and privacy/auth constraints. It is nearly complete; only explicit sibling differentiation and result-shape nuance are missing, which is minor.

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%, so the schema already documents all six parameters in detail, including formats and constraints. The description only loosely restates url, since, and the digest option without adding syntax or semantics beyond the schema, so the baseline 3 is correct.

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 states a specific verb and resource: checking whether an MCP server's tools changed since a given date, framed as a pre-connection check. It is clear about what it does, but it does not differentiate itself from close siblings such as gaip_manifest_changes or gaip_compare_supplier_snapshots.

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?

"Use this before connecting to an MCP server" gives an explicit usage context and timing. However, it names no alternatives and states no when-not condition, so the agent must infer how it differs from the overlapping manifest-change sibling.

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