get_deleted_posts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the 'last_id' parameter for pagination-like behavior but fails to describe critical traits such as authentication needs, rate limits, error conditions, or the format/scope of returned data (e.g., are all deleted posts returned or only user-accessible ones?).

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 extremely concise with two sentences that directly address the tool's function and a key parameter. It is front-loaded with the core purpose and avoids any redundant or unnecessary wording, making it 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?

Given the tool's complexity (retrieving deleted data with pagination), lack of annotations, and no output schema, the description is incomplete. It misses essential context like what 'deleted posts' entails (e.g., soft vs. hard deletion, timeframes), behavioral constraints, and output details, leaving significant gaps for agent understanding.

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 description coverage is 50% (only 'last_id' has a description in the schema). The description adds meaning by explaining 'last_id' usage ('get everything deleted above that post ID'), which clarifies its pagination role. However, it doesn't address the 'limit' parameter at all, leaving half the parameters without semantic context beyond the schema.

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 ('Retrieve') and resource ('deleted posts'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'search_posts' by focusing specifically on deleted content, though it doesn't explicitly contrast with all siblings.

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 no guidance on when to use this tool versus alternatives like 'search_posts' or 'get_comments'. It mentions a parameter usage ('Pass last_id...') but offers no context about appropriate scenarios, prerequisites, or exclusions for tool selection.

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