Accept a credential issued to this account (writes to the ledger)

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

With no annotations, the description carries the full burden and does: it flags the write to the ledger and the XRP spend, discloses that signing material comes from the OS keychain and is never exposed to the agent, and documents both gating flags (--allow-writes for the tool, --allow-inline-seed for the seed argument). This is exactly the behavioral context annotations would otherwise supply.

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?

Front-loaded with the destructive consequence in capitals before any mechanics, then the lifecycle rationale, then the seed/flag caveats, then the sibling routing. Every sentence carries distinct information; nothing repeats the schema or the title.

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?

An output schema exists, so return values needn't be described, and the safety/availability picture is thorough for a mutation tool with no annotations. The remaining gap is the undocumented issuer/credential_type/network semantics, which matter for correctness on a ledger write.

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 description coverage is 0%, so the description must compensate and it only partly does: it explains the optional `seed` argument's purpose and the condition under which it is refused, which is high-value. But `issuer`, `credential_type` and `network` get no explanation at all — an agent must infer whether credential_type is free-form, a hex value, or an enum, and what network's empty default means.

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 verb+resource (accept a credential issued to this account) and immediately explains the lifecycle position: a credential from issue_credential is not valid until the subject signs, and this submits the CredentialAccept. That distinguishes it from issue_credential, get_credential and revoke_credential without opening any schema.

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?

Explicitly names alternatives and the conditions selecting them: get_credential to read state without changes, revoke_credential to withdraw, and issue_credential as the counterpart operation this complements. It also states a hard availability precondition (server must be started with --allow-writes), which is the kind of when-you-can-use-this guidance agents usually have to discover by failing.

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