Get service details

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

With no annotations, the description carries the burden, and it discloses the response contents and the read-only nature implied by 'get' and 'full detail'. It does not explicitly mention authentication or wallet requirements, which are relevant with x402 terms, but the core behavioral contract is clear.

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 with no filler: the first enumerates return content, the second gives the targeted when-to-use directive. Every sentence earns its place and the key term is include-detail.

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 one-parameter lookup tool with a fully described schema, the description is sufficient: it names the parameter source, return content, and the exact invocation point relative to siblings. It leaves only auth/wallet requirements to be discovered, but the x402 settlement-terms hint provides some lead.

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 100%, so the single param is already fully documented. The description does not repeat it or enrich it, only referring to 'the input matches the schema'. The baseline is 3 because the schema carries the parameter semantics.

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 states a specific verb and resource: it retrieves full detail for one service. It enumerates what is returned (input/output JSON Schema, price, example request/response, documentation, x402 settlement terms) and distinguishes itself as the single-service lookup ahead of try_service or call_service.

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?

It gives an explicit when-to-use directive: 'Call this before try_service or call_service so the input matches the schema.' This names the relevant sibling alternatives and tells the agent the condition that selects this tool.

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