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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds the billing model (paid per call, x402 vs license_key), that it 'reads the map only' (no live probing of servers), and the high likelihood of an empty result. It does not state rate limits or the 30-day window itself, which lives in the schema.

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-loaded with the use case and batched value proposition, followed by the cost caveat and read-only note. Dense but every clause carries information; only the 'instead of one by one' phrasing is slightly redundant with the batch framing.

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 the description carries the return-value burden and does so by listing the change categories (outages, recoveries, tool adds/removes/changes, risk increases, silent changes). The nested last_trip reporting object is fully documented in the schema, and payment handling is covered. Slightly thin on the shape/format of the returned delta.

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 servers, since, last_trip, and license_key in detail, including the 30-day lookback and 50-item cap. The description echoes the two key parameters but adds no syntax or format detail beyond the schema, so the 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 and resource: check what changed on MCP servers, in a single batch call instead of one by one. The batch framing distinguishes it from per-server siblings like my_server_report or watch, though no sibling is named directly. The parenthetical enumeration of change types makes the scope unambiguous.

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 clear context: use it with up to 50 servers plus your last check date to get a delta, and it names list_paid_tools for the pricing path. It also sets the expectation that most answers are 'nothing changed'. No explicit when-not or alternative-tool guidance beyond the one-by-one contrast.

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