Get a post

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

With no annotations, the description adds useful context by requiring the 'posts:read' scope and noting included fields (content_html/content_json and SEO fields). However, it does not disclose behavior for non-existent IDs, error responses, or output format, leaving gaps.

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 two sentences with no redundant wording. It front-loads the main action and then adds the auth requirement in a separate concise sentence, making it efficient and easy to scan.

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 low complexity (single parameter, no output schema, simple read), the description is mostly complete: it covers the core operation, auth scope, and returned fields. It lacks explicit error handling details, but these are not critical for a simple fetch.

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 schema already fully describes the single 'id' parameter with 100% coverage. The description repeats 'PocketBase record ID' but does not add additional semantics beyond the schema, so baseline 3 applies.

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 it 'Fetches a single post by its PocketBase record ID', which is a specific verb+resource+scope. It distinguishes from list_posts (single vs. list) and sibling mutation tools like create_post and update_post.

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?

Usage is implied for retrieving a single post by ID, but no explicit alternatives or exclusions are mentioned. The description does not say when to prefer this over list_posts or other siblings, providing only implicit context.

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