content_read_post

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

No annotations, so description covers read-only nature, public access, only published posts, and return structure. Could add details on rate limits or auth, but sufficient for a read-only public endpoint.

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?

Well-structured with sections, no redundant sentences, front-loaded key info, and only essential details.

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 adequately describes return (single post object with requested fields and related data). All aspects of usage and constraints are covered.

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 100% but description adds value: explains id/slug mutual exclusivity and the purpose of include, fields, and formats parameters.

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?

Clear verb 'Read' and resource 'single published post'. Distinguishes from siblings (different resources: pages, tags, authors) and explicitly mentions admin_read_post for draft/scheduled 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?

Provides explicit use cases, mutual exclusivity of id/slug, access constraint (published only), and alternative for drafts via admin_read_post.

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