get_service

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

The readOnlyHint annotation already indicates a safe read operation, and the description aligns with that by mentioning returning a record. It adds detail about the content but no new behavioral caveats.

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 succinct, two sentences, with no redundant information. It efficiently conveys the purpose and parameter usage.

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?

The description covers what the tool does and the required parameter. It does not mention return format, errors, or pagination, but for a simple record retrieval this is likely sufficient given the domain is well-defined.

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 single parameter 'domain' is clearly explained as the host/domain to look up, and the description reinforces this with an example (api.nansen.ai). The schema also provides a description, so meaning is fully covered.

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 returns a full unified record for a service, listing specific details like settlement rails, reputation, price, buyers, volume, and coming-soon chains. This distinguishes it from sibling tools like find_paid_service or directory_stats.

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 provides parameter usage ('Pass the host (domain)') but does not explicitly state when to use this tool versus alternatives. However, the purpose is specific enough that an agent would infer when to call it.

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