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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds value by noting that 'Equipment and instances remain independent' (indicating no side effects) and that it returns the Grip Studio link, which clarifies the output behavior beyond 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?

Three sentences, no filler. The purpose is front-loaded in the first sentence, the behavioral note is second, and the alternative routing is last. Every sentence earns its place, and the entire description fits in two lines.

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 read-only tool with annotations covering safety and idempotency, the description is nearly complete: it states what is read, notes immutability, gives the return value, and routes to the correction tool. The only missing piece is a clear explanation of the required id parameter, but given the simplicity of the tool, this is a minor omission.

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?

The description does not explain either parameter. The schema describes workspace_id ('Workspace authorized by the current key') but id has no description, and the description does not clarify that id refers to the kit identifier. With schema coverage at 50% and no compensation in the description, the agent must infer the meaning of id from context, which is a notable gap.

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 opens with the specific verb 'Read' and the resource 'owned kit manifest, semantic slots and immutable piece revisions', which clearly identifies what the tool does. It also differentiates from the sibling gripforge_armor_generate by explicitly stating when to use that tool for corrections, so an agent can distinguish it from other armor-related tools.

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 final sentence gives an explicit routing instruction: 'To correct selected types, call gripforge_armor_generate with source_kit and pieces.' This tells the agent exactly when to use an alternative and what parameters to pass, leaving no ambiguity about when this read tool is appropriate.

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