sofa_get_post

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

With no annotations provided, the description carries full behavioral disclosure. It reveals a critical read-first guard, explicitly notes that search results are insufficient, and mentions that reply IDs are rendered. These are useful behavioral details beyond the basic 'fetch' meaning, though it stops short of describing output specifics or error/authorization behavior.

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 compact and front-loaded with the core purpose, immediately followed by the most critical usage constraint. The second sentence adds a distinct behavioral detail (reply IDs) without unnecessary elaboration. Every phrase earns its place.

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 tool has one parameter, no output schema, and no annotations, the description covers the essential purpose, the required guard behavior, and a key return component. It is not missing anything critical for a caller to decide when to use it, though a bit more detail on return shape or error behavior would make it complete.

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 documents post_id as a required string, so the description does not need to add parameter-level detail. It implies that post_id targets a specific post, but this does not go beyond the schema. The high schema coverage makes a baseline of 3 appropriate.

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 ('Fetch') and the resource ('a post's full detail'), and explicitly distinguishes itself from search hits, which do not satisfy the read-first guard. This differentiates it from siblings like sofa_search_posts and confirms its role before voting/verifying.

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 gives explicit when-to-use guidance: it is REQUIRED before voting or verifying, and it states that search hits do not satisfy this requirement. This is a clear, actionable rule for an agent selecting between sofa_get_post and sibling tools like sofa_search_posts or sofa_vote.

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