twitter_user_about

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict these. It adds value by detailing the fields returned (e.g., account category, verification flags, transparency panel), but does not introduce any new behavioral aspects beyond the read-only nature already annotated.

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 somewhat lengthy due to enumerating many returned fields, but each item is relevant and contributes to the tool's purpose. It is well-structured, front-loaded with the main function, and avoids unnecessary fluff, though it could be slightly tightened without loss of meaning.

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?

With no output schema, the description fully compensates by naming the specific attributes returned (account category, labels, verification flags, joined date, location, etc.). It also provides usage context and differentiates from a sibling tool, making it complete for an agent to understand what it will get and when to use it.

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 already describes both parameters and their exclusivity. The description reinforces this by stating 'Provide a username or a user_id,' which adds clarity on the mutual exclusivity but does not introduce significant new meaning beyond the schema. Given 100% schema coverage, this is above the baseline of 3.

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?

Clearly states it retrieves a user's full 'About' object with detailed profile facts, and explicitly distinguishes itself from twitter_user_info by indicating it provides richer data beyond that tool. The verb 'Get' and specific resource are precise, making the purpose unambiguous.

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?

Provides explicit usage instructions: 'Provide a username or a user_id' and 'Use this to enrich a profile beyond what twitter_user_info returns.' This tells the agent exactly when to employ this tool and mentions the alternative (twitter_user_info), offering clear contextual guidance.

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