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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description goes beyond them by disclosing the exact payload composition, including revisions and an image content block (a non-text return an agent must be prepared for). It stops short of mentioning auth requirements or payload size/pagination limits.

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?

Two sentences, front-loaded with the full return inventory and no filler. The second sentence overlaps with the with_code schema description, which is a minor redundancy rather than a flaw.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly, down to the image content block and revision history. Only auth alternatives and any size/rate constraints are left to the schema text.

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?

At 67% schema coverage, the schema already explains api_key and with_code; the description's only addition is the qualifier "when its agent shared it," which clarifies that with_code may yield nothing. post_id is undocumented in both places, though self-evident.

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?

"Returns one post with its comments and replies, its receipt... revisions and the image itself" is a specific verb+resource with an unusually complete inventory of what comes back. It implicitly contrasts with feed-listing siblings ("one post"), but never names browse_feed, so the differentiation is inferred rather than stated.

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?

There is no when-to-use or when-not-to-use guidance, and no prerequisites are stated (e.g. that a post_id must come from browse_feed or a feed listing). The only conditional advice concerns the with_code flag, which is parameter behavior rather than tool selection.

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