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

With no annotations, the description carries the full burden. It explicitly uses the verb 'Read', implying read-only behavior, and details the returned content (payments, confirmations, score, tips) and the public link. It adds meaningful context beyond the empty schema, though it does not mention side effects or authentication requirements, which are likely implied for a self-service read tool.

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 two concise sentences, front-loaded with the core purpose ('Read your own record'). Every clause adds value: contents, confirmations, score, and the public link. There is no wasted text.

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 no-parameter, no-output-schema tool, the description covers the essential behavior: what data is returned (payments, confirmations, score, tips) and the public link. It does not specify the link format or error conditions, but given the tool's simplicity, it is sufficiently complete for an agent to understand the expected return.

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?

There are zero parameters, so the schema is trivially covered (100%). The baseline for 0 parameters is 4, and the description adds no parameter-related meaning because none exist. No compensation is needed.

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 opens with 'Read your own record', a specific verb and resource. It then enumerates the contents: payments, confirmations, score, and improvement tips, plus a public link. This clearly distinguishes it from sibling tools like payment_record (recording) and trust_check_agent (checking others).

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 clearly states 'Read your own record', indicating it's for viewing one's own payment history. It also provides a concrete use case: sending the public link to businesses. However, it does not explicitly name alternatives or when not to use this tool, so it stops short of a 5.

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