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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: the call is free and requires no x402 challenge, which matters in an ecosystem where sibling tools are paid. It also gives the HTTP equivalent endpoint. It stops short of saying whether the document is static/cacheable, what format it is returned in, or whether the result is deterministic.

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 resource identity is front-loaded and the two supporting sentences (free access, HTTP equivalent) are both useful. The middle clause ('the rules every paid answer is reproducible from, and the pinned public test corpus identity') is dense and slightly awkward but earns its place by explaining what the criteria actually contain.

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 zero-parameter document fetch with no output schema, the definition covers purpose, cost model, and the equivalent HTTP URL. The remaining gap — response format and whether the criteria are versioned/immutable — is minor at this complexity level.

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 input schema has zero parameters, so the baseline is 4. The description adds a small amount of relevant context (the service version path composite-inventory/v1 and the HTTP equivalent) but there are no parameters whose meaning could be clarified.

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 names the specific resource — the published criteria for the Composite Inventory service (composite-inventory/v1) — and characterizes its content (reproducibility rules plus the pinned test corpus identity). That is enough to separate it from composite_inventory_lookup and composite_inventory_precheck, though it never uses an explicit verb like 'returns', leaving the action implied rather than stated.

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?

There is no guidance on when to call the criteria endpoint versus the sibling lookup or precheck tools, and no description of what an agent should do with the criteria document. The only usage-adjacent statement is the payment note ('call directly without payment'), which is an access instruction rather than a when-to-use rule.

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