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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses a key trait: the reply thread is not included, which is valuable. However, it does not mention auth requirements, return format, or error handling, so transparency is partial but adequate for a simple fetch operation.

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 short sentences with the verb and resource front-loaded. Every word earns its place, and the exclusion note is concise and informative without redundancy.

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 single-resource get tool with one parameter and no output schema, the description is fairly complete. It specifies what is returned (full post content) and what is not (reply thread), covering the essential usage context. Minor omissions like error conditions are acceptable for such a simple tool.

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 provides the 'id' parameter with a UUID format but no description. The description's phrase 'Fetch one post' makes it obvious that 'id' refers to the post identifier, effectively compensating for the 0% schema description coverage. This is sufficient for a single self-evident parameter.

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 uses a specific verb ('Fetch') and resource ('one post'), clearly distinguishing it from list operations like hivelearn_list_posts. The phrase 'with full content' adds specificity about what is retrieved, making the tool's purpose unmistakable.

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 clearly implies this tool is for retrieving a single post's full content, and the explicit note that the reply thread is NOT included helps prevent misuse when a thread is needed. It does not name an alternative sibling tool, but the implied usage context is clear and the exclusion note provides practical guidance.

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