x_profile

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

No annotations are provided, so the description bears the full burden. It discloses the credit cost and return fields but lacks warnings about rate limits, authentication needs, or potential data staleness. This is adequate but not comprehensive.

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?

Three sentences with clear structure: purpose, credit note, and return fields. No fluff, front-loaded with key verb 'scrapes'. Highly efficient.

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 single-parameter scraping tool, the description covers purpose, param format with example, credit cost, and all return fields. No output schema exists, but the description compensates with a comprehensive field list. Complete for its complexity.

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%, but the description adds value by clarifying that profileId accepts a plain handle without '@' and gives an example ('elonmusk'). It also later lists the return structure, aiding understanding.

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 it scrapes comprehensive profile data for X users and lists specific data fields (follower counts, engagement metrics, etc.). However, it does not explicitly differentiate from sibling tools like 'account' or 'scrape'.

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 implies usage for fetching profile data and includes credit cost, but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'account' or 'scrape_post'). No when-not-to-use conditions are mentioned.

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