Openapi Summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is clear. The description adds useful behavioral context: 'may expose x402 utility pricing.' This goes beyond annotations. No contradictions.

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 consists of two concise sentences: the first clearly states the purpose, and the second provides relevant context about pricing and separation from other protocols. No unnecessary words or details.

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 tool's simplicity (2 parameters, no output schema), the description covers the main functionality and adds context about pricing. However, it could be slightly more complete by mentioning the output format or structure of the summary, but this is not critical for selection.

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 both parameters (url and timeout) described adequately in the input schema. The description does not add additional meaning beyond the schema, such as explaining how the URL should be formatted or what the timeout influences. Baseline score of 3 is appropriate.

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 the tool's purpose: 'Summarize an OpenAPI document including title, version, paths, tags, and likely auth surface.' It uses a specific verb ('Summarize') and resource ('OpenAPI document'), and the inclusion of specific elements distinguishes it from sibling utility tools that handle different aspects of APIs.

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 context by mentioning that Delx Agent Utilities are separate from the free witness protocol and may expose x402 utility pricing, which hints at when to use the tool (as a utility) but does not explicitly state when to use this tool over alternatives or when not to use it.

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