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

Annotations indicate readOnlyHint=false and destructiveHint=false; the description confirms it's a write operation to IPFS. It adds the prerequisite chain context but does not detail other side effects or permissions needed.

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, front-loaded with the main action, prerequisite, and return format. Efficient but could be slightly more structured with explicit parameter guidance.

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?

With 17 parameters, nested objects, no output schema, and low coverage, the description leaves many gaps. The agent lacks information about most parameters and the overall metadata structure. Incomplete for reliable invocation.

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 only 12%, with 15 out of 17 parameters lacking descriptions. The description only mentions the 'items' array briefly. It does not explain critical parameters like schemaUrl, bundleUuid, or nested seller object fields.

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 'Stores a Bundle metadata object to IPFS' with a specific verb and resource. It distinguishes from siblings like store_bundle_item_product_v1_metadata by noting them as prerequisites.

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?

Explicitly provides a prerequisite (calling store_bundle_item_* first) and explains how their returned URLs are used in the items array. Also states what it returns ({ metadataUri, metadataHash }).

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