Checksum and Verify Pack

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

Annotations indicate write (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that compute writes a manifest and verify re-hashes for comparison, and that no TD bridge is needed, providing useful behavioral context beyond annotations.

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?

Two sentences efficiently convey the core functionality and actions. Could be improved by briefly listing key parameters or providing a more structured summary, but it is clear and direct.

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?

Given the complexity (9 params, nested objects, no output schema), the description covers the main workflow but lacks details on parameter usage, default exclusions, and manifest format. It is minimally complete for a basic understanding but not fully sufficient.

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 has 9 parameters with 0% description coverage. The description only implicitly mentions 'action' and 'path', leaving other parameters like strict, manifest, exclude_globs, etc. unexplained. This does not compensate for the lack of schema descriptions.

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 computes or verifies SHA-256 checksums for tdmcp artifacts, with specific actions compute and verify. It distinguishes itself from sibling tools by focusing on checksum operations for packaging artifacts.

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?

It explains that action=compute writes a manifest and action=verify reports mismatches. It also mentions 'No TD bridge required,' but does not explicitly state when to use this tool versus alternatives or provide exclusions.

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