get_categories

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

The description implies a read-only operation and specifies the output (post counts, metadata). Without annotations, it carries the burden, but it adequately discloses the behavior for a simple retrieval.

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, concise sentence that effectively communicates the tool's purpose without unnecessary words.

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 description explains the return values ('with their post counts and metadata'), which is sufficient for a simple tool with no output schema. It could mention idempotency, but not required.

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?

Given zero parameters and 100% schema coverage, the description adds value by detailing the output (post counts, metadata) beyond the empty 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 action 'Get all blog categories' and specifies the returned data includes 'post counts and metadata', which distinguishes it from sibling tools like get_posts or get_dashboard.

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 indicates it retrieves all categories with no filtering, implying use when a full list is needed. It doesn't explicitly state when not to use, but the context is clear given no parameters.

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