get_reef_post

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

With no annotations, the description should compensate but does not. It fails to disclose whether the operation is read-only, requires authentication, or what happens on missing post_id. The phrase 'with comments' is helpful but insufficient.

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 concise (one sentence, 6 words) and front-loaded, but it omits necessary information, making it under-specified rather than optimally concise.

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?

Despite the tool's simplicity (one parameter, no nested objects), the description lacks completeness. No output schema is provided, and the description does not explain the return structure, error handling, or any prerequisites, leaving significant gaps.

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 has 0% description coverage and the description adds no meaning to the 'post_id' parameter. It does not mention format, origin, or constraints, leaving the agent without guidance beyond the type string.

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 the verb 'Get' and the resource 'a single reef post with comments', making its purpose unambiguous. It distinguishes from sibling tools like get_reef_feed (multiple posts) but does not explicitly differentiate from other single-post getters.

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 guidance is provided on when to use this tool versus alternatives, such as other get_reef_* tools or when a specific post_id is available. The description lacks context for appropriate invocation.

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