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

With no annotations, the description carries the full transparency burden. It lists what the contract covers, giving some insight into the content, but it does not explicitly state that this is a read-only operation, mention any prerequisites or side effects, or describe the return format. 'Return' implies a safe read, but the description could be more explicit.

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 sentence and relatively concise. However, the list of contract topics is somewhat awkwardly packed into one sentence ('catalog, direct x402 purchase, payer-ownership, fulfillment, and privacy contract'), which could be restructured for better readability but is still efficient.

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 zero-parameter, no-output-schema tool, the description provides a reasonable overview of what the contract covers. It lists the major aspects, giving an agent enough context to understand the tool's purpose. It does not explain the return format, but the absence of parameters and output schema means less is needed. It is complete enough for a simple contract retrieval.

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 input schema has zero parameters, so there is nothing to describe. Per the calibration, a zero-parameter tool receives a baseline score of 4. The description does not need to add parameter context since none exist.

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 the Freeland eSIM contract and lists its key topics (catalog, purchase, ownership, fulfillment, privacy). It is specific about the resource but does not explicitly differentiate from sibling tools like get_agent_contract, though the 'Freeland eSIM' qualifier helps narrow it down.

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 guidance on when to use this tool versus alternatives, such as get_esim_readiness or get_agent_contract. There is no mention of scenarios where this contract would be needed over other tools.

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