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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds modest context—'indexed' and 'verified provenance'—but does not clarify error behavior, not-found handling, or what exactly 'verified provenance' contains, which a no-output-schema tool should disclose more fully.

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 description is a single eight-word sentence with no filler, leading with the action and then specifying the target. It is appropriately sized for a tool with one parameter.

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 simple, one-parameter, read-only tool the core purpose is stated, but without an output schema the description should explain return shape, failure modes, and the meaning of 'verified provenance' more explicitly. The oddity of having zero required parameters is also left unexplained.

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 0%, and the only parameter, serviceId, has no description and is not marked required. The description does not mention the parameter, its format, or why no required fields are declared, so it fails to compensate for the schema's lack of detail.

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, 'Inspect', and a specific object, 'one indexed service and its verified provenance', making it clear this is a single-item read operation. The singular 'one' differentiates it from search_verified_offers, and the 'service' versus 'provider' wording helps separate it from get_verified_provider, though siblings are not named explicitly.

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 description provides no explicit guidance on when to use this tool versus alternatives like search_verified_offers or get_verified_provider. The phrase 'one indexed service' only faintly implies a single-lookup use case but gives no prerequisites, exclusions, or routing hints.

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