pages_get_post

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'Get' implies a read-only operation, but it does not disclose potential errors (e.g., invalid post_id), authentication requirements, or limitations on the returned details. This minimal disclosure is not misleading but lacks richness.

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 is front-loaded with the key action and object. There is no redundancy or irrelevant information, making it appropriately sized for a simple get operation.

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?

Given the lack of an output schema and annotations, the description should clarify what 'details' includes or what response format to expect. It does not, leaving the agent uncertain about the return value or potential edge cases. For a simple tool, this is a notable gap in completeness.

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 compensate by explaining the post_id parameter. It merely says 'single post,' which indirectly references the parameter but gives no guidance on the format, source, or meaning of post_id beyond the schema's type definition. The description adds essentially no value for parameter understanding.

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 'Get details of a single post' clearly states the action (get) and the resource (a post), distinguishing it from sibling tools like pages_list_posts and pages_delete_post. It precisely conveys the intended operation without ambiguity.

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?

No explicit usage guidance is provided. The description implies use when you need details of a specific post, but it does not mention alternatives, exclusions, or prerequisites like finding the post_id first. The usage context is only minimal and not clearly differentiated from related tools.

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