get_recent_posts

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

With no annotations, the description carries the full burden. It only repeats schema-visible constraints (default/max limit) and implies a read-only operation via 'Retrieve'. It does not disclose error behavior, pagination, ordering semantics, or any edge cases.

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?

One sentence with all key info front-loaded. No filler or redundancy.

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?

The tool is simple (2 optional params) and the description covers the essential invocation details. An output schema exists, so return values need not be described. Missing behavioral notes (e.g., ordering, auth) are minor given the straightforward read-only purpose.

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?

The description gives semantic meaning to both parameters by naming 'category slug' and stating limit constraints, but this largely overlaps with the schema's pattern/default/max. Since schema description coverage is 0%, it adds some value but not enough to fully compensate.

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 action ('Retrieve recent Doctor of Credit posts') and specifies the optional category filter, making it distinct from sibling tools like get_post (single post) and search_posts (search-based).

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?

It provides clear context (recent posts, optional category slug) but does not explicitly mention when not to use it or compare to alternatives like search_posts. The guidance is inferred from the description rather than stated.

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