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

With no annotations, the description carries the full behavioral burden. It usefully discloses a pricing/quota trait ('5 free trial calls per signed wallet') and implies a read-only fetch, but it does not explain authentication mechanics, error behavior, or what happens when the user is not found.

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 a single front-loaded sentence with the core action first and a useful quota note appended. It is appropriately sized for a simple lookup tool, though the free-trial emoji is slightly informal.

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 simple profile lookup with no output schema, the description helpfully lists returned fields and mentions quota. However, it does not resolve the opaque input and fid parameters, and it omits details about the signed-wallet requirement implied by the free-trial note.

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 for three undocumented parameters. It only clarifies that username is the lookup key, while fid and the generic input parameter remain completely unexplained.

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 description states a specific verb ('Fetches') and resource ('a Farcaster user') and names the lookup key ('by username'). It also lists the returned fields, making the tool's identity clear against the many unrelated x402-* siblings.

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 phrase 'by username' implies the primary usage context, but there is no explicit when-to-use or when-not-to-use guidance. It also does not explain whether fid or input are alternatives to username, leaving some ambiguity despite the clear core purpose.

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