scrape_post

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

Description says 'Fetch' (read-only behavior), but annotations set readOnlyHint=false, creating a contradiction. No additional behavioral traits beyond the contradiction are disclosed (e.g., rate limits, auth, side effects).

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, direct and front-loaded. Every word adds value. No fluff.

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?

No output schema, but description does mention return type (post data and comments). However, lacks details on comment structure or pagination. For a 3-parameter tool with full schema coverage, it's adequate but not comprehensive.

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% with clear parameter descriptions. The description adds no extra meaning beyond the schema; it only states the return type. Baseline 3 is appropriate.

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 fetches a specific Reddit post by URL, and distinguishes from siblings like get_posts (which likely fetches multiple) and scrape_subreddit (subreddit-level). Verb and resource are specific.

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?

Implies use when you have a specific post URL, but lacks explicit guidance on when to use alternatives like get_comments for only comments, or when not to use. No exclusions or prerequisites mentioned.

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