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

With no annotations, the description carries the full burden, and it does disclose cost ('Free'), read access ('readable by any seller with ledger_entry'), and the full return surface (standing, issued credential with CredentialCreate hash, acceptance steps, unlock challenge). It omits auth/rate-limit specifics and never explicitly confirms read-only behavior, keeping it from a 5.

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?

It is front-loaded with the 'Free' cost signal and then packs purpose, credential mechanics, and return contents into two dense sentences with little waste. The jargon makes it heavy, but nothing is redundant.

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?

With no annotations and no output schema, the description usefully enumerates return contents, which is the main gap it needed to fill. However, it leaves the input parameter's semantics (optional account, default behavior) and any access/prerequisite conditions unexplained for a fairly specialized credential tool.

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 'account' parameter has 0% schema description coverage, and the description never explains whose account it is, that it is optional (required=0), or what happens when it is omitted. For a schema with an undocumented parameter, the description fails to compensate.

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?

States a specific resource (the ProvenPayer credential / XLS-70 standing) and what is returned, so an agent knows this reports credential state rather than performing a payment or verification. It does not explicitly differentiate itself from siblings like get_verification or prove_xrpl_transaction, and the jargon (Plumb-proven, ledger_entry) assumes domain familiarity, so it falls short of a 5.

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?

Only implicit signals exist: 'Free' and 'readable by any seller with ledger_entry' hint at cost and access, but there is no explicit statement of when to call this versus siblings such as get_verification or prove_xrpl_transaction. No exclusions or alternatives are named.

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