Message to sign for the Agent badge

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns a signable message and adds workflow/prerequisite context, but it does not cover authentication needs, validation behavior, idempotency, or exact return format.

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?

The description is front-loaded with purpose, then gives next steps and a prerequisite in three compact sentences. There is no obvious filler, though it could be slightly more structured.

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 two-parameter tool with no annotations and no output schema, it supplies useful purpose and workflow context. However, it leaves parameter-level guidance and behavioral details under-specified.

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. It indirectly identifies wallet as the agent wallet and xHandle as the X account, but it adds little about formats, handle syntax, or constraints beyond what the schema's wallet pattern already provides.

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?

The first sentence states a specific verb and resource: it returns the message the agent wallet must sign. The title and description tie it to the Agent badge, but the description does not explicitly contrast it with prepare_metadata_message, so sibling differentiation is only implicit.

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?

It gives a clear downstream workflow: post the wallet address from the X account, then call apply_badge with the post URL. This makes the tool's position before apply_badge clear, though it does not state exclusions or explicitly compare alternatives.

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