fetch_user_posts

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

With no annotations, the description carries the burden. 'Fetch' implies a read-only operation and 'from external API' signals potential network dependency, but auth requirements, rate limits, error behavior, or pagination are not disclosed. It provides some context but not comprehensive behavioral detail.

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 brief and front-loads the main purpose. The Args block is somewhat redundant with the schema but is clearly structured and does not add significant verbosity.

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 single-parameter fetch tool with an output schema, the description is adequate but not thorough. It omits external API specifics such as authentication, rate limits, pagination, or failure modes, though these may be less critical given the tool's simplicity.

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 has 0% description coverage, so the description must compensate. It explains user_id as 'The user ID to fetch posts for', which adds basic role semantics beyond the schema's type and title. However, this is minimal and largely inferable from the tool name, and it does not add constraints or format details.

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?

Description uses a specific verb ('Fetch'), a clear resource ('posts'), and a scope ('for a specific user from external API'). This distinguishes it from sibling tools like detect_dark_patterns and classify_pattern, which are clearly analysis/classification operations.

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 gives no guidance on when to use this tool versus alternatives. It does not mention any of the sibling tools or conditions under which this tool is preferred, leaving the agent to infer from names alone.

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