twitter_user_about

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

The description adds context beyond the annotations (readOnlyHint, openWorldHint) by detailing the type of data returned (account category, professional labels, joined date, location). No contradiction with annotations.

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 concise (two sentences), efficiently front-loading the purpose and usage, with no unnecessary words.

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?

Given the absence of an output schema, the description adequately covers what data to expect (fields like account category, labels, joined date, location) and the tool's purpose relative to siblings, making it complete for the agent.

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 coverage is 100% and parameters are simple. The description reiterates the mutual exclusivity of username and user_id, but does not add significant new meaning beyond the schema's own descriptions.

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 clearly states the verb 'Get' and the resource 'user's About panel', listing specific data fields (account category, labels, joined date, location) and explicitly distinguishes from the sibling tool 'twitter_user_info'.

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 provides explicit guidance: 'Use this to enrich a profile beyond what twitter_user_info returns', naming the alternative tool and specifying the context for use. It also instructs to provide exactly one of username or user_id.

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