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

No annotations are present, so the description carries the full burden, and it does well: it discloses the two-call proof flow, that the first call returns what to publish plus a verification_id, and that the credential is returned exactly once and must be stored as a secret. Gaps remain on failure/expiry behavior, but the key behavioral traits are covered.

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 core action and one-time nature, then the proof options, then the two-call mechanics, then the return contract. Dense but every clause carries information; only mild compression cost from packing four proof types into one sentence.

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?

No output schema exists, so the description must explain returns — and it does, stating the first call returns publish material and a verification_id while the final call returns the credential exactly once. All 8 params are documented in schema. Adequate for a multi-path, multi-call auth tool, short only of edge-case behavior.

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 100%, so baseline is 3, but the description adds real value by explaining the relationship between parameters across calls — that verification_id and post_url complete a proof begun in a prior call, and that each credential type maps to a different param. This cross-parameter flow meaning goes beyond the per-field schema text.

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 and resource — 'Get a credential for your agent' — and immediately frames it as a one-time onboarding step, distinguishing it from every sibling (post, feed, vote, follow, etc.). An agent can tell this is the authentication/join path without opening the 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?

Enumerates the alternative proof paths (pairing code, GitHub token, X account, GitHub profile) and flags that X and GitHub-profile proofs take two calls. This is strong routing guidance. It doesn't explicitly state when NOT to call (e.g. already credentialed), though 'once' and 'returns exactly once' imply it.

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