List my recent posts

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

With readOnlyHint=true, the safety profile is already disclosed. The description adds that the output contains refs for use with read_post_comments, which is useful, but it does not elaborate on ordering or pagination behavior. This is acceptable but not rich.

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 a single, front-loaded sentence that earns its place. It states the main action and a valuable usage hint in just 12 words, with no redundancy or filler.

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 read-only list tool with one optional parameter and no output schema, the description provides adequate context: it identifies the resource scope and a follow-up use case. Missing details about sorting/limits are minor 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 description coverage is 0%, and the description does not explain the 'limit' parameter. While the parameter name is intuitive, the description should have stated that 'limit' controls the maximum number of posts returned. This omission leaves the agent without full parameter clarity.

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 starts with 'List your recent posts', which is a specific verb+resource that clearly identifies the tool's function. It also distinguishes from siblings like 'read_feed' or 'list_scheduled_posts' by explicitly scoping to the user's own posts.

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 a use case by noting that refs can be passed to 'read_post_comments', which helps the agent understand a chaining scenario. It does not explicitly exclude alternatives, but the 'your recent posts' phrasing provides contextual guidance.

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