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

With no annotations, the description carries the full burden. It usefully discloses the key behavior (recursive traversal, detection of sensitive changes that occur without a version bump) and the cost (0.002 USDC), but says nothing about return shape, error modes, or what happens with malformed manifests.

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 that packs purpose, precondition, core detection behavior, and price with no filler. Slightly dense but every clause carries information.

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 nested-object analysis tool with no annotations, no output schema, and 0% parameter coverage, the description is serviceable but thin. It communicates the value proposition (sensitive-change detection) yet leaves the input structure and result format largely unexplained, which matters given the nested schema.

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 0% and both parameters are nested objects requiring a 'version' field. The description only implies that versions are mandatory; it never explains what 'current'/'previous' manifest objects should contain or how recursion over nested tools is interpreted. Compensation is partial at best.

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+resource ('Recursive manifest diff') and adds scope detail: it requires explicit versions and flags sensitive changes lacking a version advance. This distinguishes it reasonably from siblings like mcp_manifest_firewall or tool_capability_drift_monitor, though it never names an alternative explicitly.

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?

No when-to-use guidance is given and no alternatives are named. The only constraint offered ('requires explicit versions') is a precondition, not usage guidance. An agent cannot tell from this text when to reach for this tool over the many manifest/security siblings.

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