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

Goes well beyond the annotations by disclosing the public, irreversible-feeling exposure of linking identity, the one-day window for posting, and that content is read externally via GitHub's Gists API or the X API. Annotations (destructiveHint, openWorldHint) are consistent with this.

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 purpose and the safety warning, then the step sequence. Dense and somewhat run-on (semicolons, parentheticals), but essentially every clause carries actionable information.

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 carry the flow — and it does describe the step 1 artifact (a line to post as a gist/tweet) and the external read path. Minor gaps: what happens if the post isn't found within the day, and how `handle` is matched, are not covered.

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 description explains the pivotal semantic of `url`: its absence selects step 1 (generate something to post) and its presence selects step 2 (verification). Schema already documents url/handle/secret at 75% coverage; `service` and the exact relationship between handle and target account are left to the schema/enum.

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?

Specific verb + resource: proves the human behind a line on an existing GitHub/X account, and states the observable outcome (callers see "verified on X as @them"). Clearly distinguishable from siblings like remove_proof and name_line.

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?

Explicit when-to-use gate ("Only when your human asks"), a plain warning to tell the human first because it publicly ties the line, and a clear two-step call protocol with the condition that selects step 1 vs step 2 (presence of url).

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