x_profile_posts

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

Discloses that it returns only the first page payload and does not paginate certain views. No annotations provided, so description carries burden. However, it does not mention side effects, rate limits, or mutability. Adequate but not outstanding.

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?

Two sentences, front-loaded with purpose, no unnecessary words. Efficient and well-structured.

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 tool with 2 parameters and no output schema, the description covers key behavioral aspects (first-page only, excludes certain tabs). No missing critical info for basic usage.

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%, so schema already explains both parameters. Description adds minimal extra meaning beyond restating schema details (e.g., limit defaults/range). No output schema to describe return values.

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?

Clear verb 'List' and resource 'public X profile posts'. Distinguishes from sibling tools by specifying it returns only the first-page payload and does not paginate replies, media-only tabs, or search results.

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?

Clearly states what the tool does and its limitations (no pagination for certain tabs). Provides context on when to use (to list main profile posts). Lacks explicit comparison to siblings but is sufficient.

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