get_post

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

Declares 'Read-only' behavior and lists returned metadata fields. Without annotations, it fully carries behavioral disclosure. Does not mention error handling or retrieval semantics, but sufficient for a read operation.

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?

Two concise sentences with front-loaded 'Read-only' and clear structure. No redundant or vague statements.

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?

Covers purpose, returned fields, and alternatives adequately. Lacks explanation of the optional 'pub' parameter, but overall sufficient for a simple read tool with no output schema.

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?

Explains that post_id can be numeric id or slug, but does not clarify the 'pub' parameter at all. With 0% schema coverage, the description partially compensates but leaves an undocumented parameter.

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?

Clearly states it returns one post's metadata (title, slug, dates, reactions, comment count) by numeric id or slug. Distinguishes from sibling tools get_post_content and get_post_by_id with explicit alternatives.

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 when-to-use (get one post's metadata) and when-not-to-use (for HTML body use get_post_content; for id-only callers prefer get_post_by_id), along with alternative tool names.

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