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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context about the returned receipt: affected packages, exact fix commands, actions/images to check, and live incidents for the detected stack.

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 two tightly written sentences: the first explains what to send, and the second explains what comes back. It is front-loaded and contains 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?

There is no output schema, so the description must explain the return value, and it does by summarizing the receipt contents. It gives enough context for an agent to understand the tool's purpose and inputs, though it does not detail error behavior or the receipt's exact structure.

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 parameter structure is already well documented. The description adds meaning by enumerating the kinds of files to include, such as lockfiles, Dockerfiles, workflows, wrangler.toml, vercel.json, next.config.*, and compose files.

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 action and scope: send project-defining files in one call and receive a consolidated receipt. It clearly implies a whole-repo check rather than a single-file check, especially through the enumerated file types and 'one receipt' framing, but it does not explicitly name or contrast with check_lockfile.

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?

The intended usage is implied by instructing the agent to send files that describe what a project runs, and the scope is clear from the file list. However, there is no explicit guidance on when to choose this over check_lockfile or when not to use it.

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