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

With no annotations, the description carries the full behavioral disclosure burden. It fails to mention error handling (e.g., username not found), rate limits, return format, or any side effects. The only extra info is billing per call, which is operational, not behavioral.

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 short and easy to scan, containing a rationale plus group/billing metadata. It is not overly verbose, but the opening sentence is a use-case statement rather than a definitive action, which slightly reduces its structural effectiveness.

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 1-parameter tool without an output schema, the description still feels incomplete. It does not clarify what the tool returns (presumably a userId) or how to handle failures. Sibling tools exist, so guidance on distinction is needed but absent.

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 schema has one parameter 'username' with zero description coverage. The description adds no semantic detail about the expected format, case sensitivity, or constraints. The parameter name is self-explanatory, but the description does not enhance it beyond that.

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 title clearly states 'Convert username to userId', but the description itself only says 'You'll need the userId to receive tweets, media and replies' – a rationale rather than a direct statement of the tool's function. It doesn't explicitly name the conversion action or distinguish this from sibling tools like get_user_by_username_username or get_user_usernames_to_ids.

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 offers no guidance on when to use this tool versus alternatives. It mentions one context (needing userId for tweets/media/replies), but does not explain when to prefer this over get_user_by_username_username or the batch conversion tool get_user_usernames_to_ids.

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