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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds the scoping detail that it returns fulfillment and payment records for a specific intent, but it does not disclose pagination, return format, or any operational constraints.

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?

A single, front-loaded sentence with no filler; every word carries meaning. For a one-required-parameter read tool this is an appropriately sized definition.

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 simple read-only purpose, one required hash parameter, and full schema coverage, the definition is adequate for basic invocation. However, it lacks usage exclusions, return-shape hints, and contrast with closely named sibling tools, so an agent must infer some context.

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 description coverage is 100%, with intentHash described as 'Intent hash' and params described as optional raw JSON merged beneath typed fields. The description's 'for an intent' adds no new semantic detail beyond those 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 uses a specific verb ('Fetch') and identifies a concrete resource ('fulfillment and payment records') scoped to an intent, so it is not a tautology. It is clear enough to distinguish from many indexer siblings, though it does not explicitly name an alternative or say what distinguishes it from peer_indexer_intents_fulfillment_amounts or fulfilled_events.

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?

No guidance is given on when to use this tool versus the many sibling indexer tools, nor are any alternatives or exclusions mentioned. The only context is the input parameter 'for an intent,' which is a constraint already visible in the schema.

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