get_post

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

With no annotations, the description carries the behavioral disclosure burden. 'Get' implies a read-only operation, and the description usefully states the returned content includes body text and metadata. However, it does not clarify behavior for missing posts, permission requirements, or what 'official' means.

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 front-loaded sentence with no redundant filler. It efficiently communicates the core action and output, though the word 'official' introduces slight ambiguity that could have been clarified.

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?

For a simple two-parameter getter, the description is serviceable, but with no output schema and no annotations it leaves out return-value structure, error behavior, and explicit alternative routing. The core information is present, yet several operational details are missing.

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%, so the description must compensate, but it does not explain the role of board or post_id beyond the schema's bare titles. The phrase 'body text and metadata' concerns the return value, not the parameters' meaning or relationships.

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 states a specific verb ('Get') and resource ('one official post') and indicates the content returned ('body text and metadata'). It implicitly distinguishes from list_posts and search_posts by focusing on a single post, though it does not explicitly name or contrast the siblings.

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 implies this tool is for fetching a single known post, especially given the required board and post_id parameters, but it provides no explicit guidance on when to choose it over list_posts or search_posts. No alternatives or exclusions are mentioned.

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