bundle_inspect

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

The description states 'Read-only — never writes pack state,' fully disclosing the safety profile. With no annotations provided, the description carries full burden and meets it well.

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 sentences long, each serving a clear purpose: first defines functionality, second gives usage guidance and safety. No wasted words.

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?

The description covers the tool's purpose and usage well. It mentions what will be summarized, giving an idea of output. However, it doesn't specify the default output format (formatted text), which could be helpful for completeness.

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% with descriptions for both parameters. The description adds context about what the tool does with the json parameter (return structured JSON), but doesn't add significant new meaning beyond the 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?

The description clearly states the tool validates and summarizes an untrusted task bundle file, listing specific aspects like schema, digest status, origin, records, and warnings. It distinguishes from sibling tools by specifying its read-only nature and that it should be called before imports.

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 description explicitly says 'Call before planning or applying an import of a bundle you did not produce,' providing clear guidance on when to use it. It implies not for bundles you produced, but it doesn't explicitly state when not to use it, so slightly less than perfect.

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