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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the remaining burden is light. The description adds genuinely useful non-obvious context: credentials are never placed in URLs or echoed in errors, which tells the agent it is safe to pass secrets and how they are handled.

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?

Three short sentences, zero filler, and the purpose is front-loaded before the authentication mechanics. Every sentence earns its place.

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 read-only tool with full annotation coverage, the credential handling is well addressed. But with no output schema, the description should say something about what the 'terminal replay' returns or its format, and it provides no disambiguation against the many sibling replay/certification readers, leaving meaningful gaps.

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 coverage is 50%: the credential parameter is documented in the schema, but 'id' has none. The description compensates for credential by explaining the two auth paths (argument vs. Authorization header), but says nothing about what 'id' identifies, leaving its semantics to be inferred from the phrase 'token-scoped certification'.

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 (read) and resource (terminal replay) scoped to a token-scoped certification, which is more precise than a generic 'get'. However, it never distinguishes itself from closely-related siblings like certification_state, certification_task, or play_replay, so the agent must infer which of the many certification/replay readers applies here.

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 explains HOW to authenticate (credential argument or Authorization header) but gives no when-to-use guidance, prerequisites, or alternatives relative to the crowded certification_* and *_replay families. Nothing tells the agent when this tool is the right choice over certification_state or play_replay.

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