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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds genuine value by acting as a return-value contract (queue position, per-network links, last error) in the absence of an output schema, though it says nothing about behavior when the post_id is not found.

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?

Front-loaded with the core action ('Get everything about one post') before the field enumeration, and the closing sentence supplies the motivating use case. The field list is long but earns its place since no output schema exists; it could be tightened with light grouping but nothing is redundant.

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 one-parameter read tool with no output schema, the description does the heavy lifting by describing the payload contents and one clear purpose. The main gap is error/empty-state behavior, which is minor for an idempotent read.

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 coverage is 100% for the single post_id parameter, and the schema already documents it as a UUID. The description adds no syntax, format, or lookup guidance beyond what the structured schema provides, so the baseline of 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?

States a specific verb and resource with explicit scope ('one post') and enumerates exactly what the response covers: status, text, thread segments, variants, media, queue status, per-network results, and last error. The single-post scope distinguishes it cleanly from the list-oriented siblings without needing to name them.

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?

Gives a concrete use case: 'check whether a post went out everywhere.' However, it does not state when not to use it or point to alternatives such as list_posts for enumeration, preview_post for drafts, or get_analytics for performance data, leaving the routing to inference.

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