get_post_feedback

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds real content-level value by specifying what the read returns (client statements, change requests, replies), but says nothing about ordering, pagination, or behavior when no feedback exists.

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?

One sentence, zero filler, and the post-scoping qualifier is front-loaded before the enumerated contents. It is a sentence fragment rather than a full statement, which is a minor structural blemish but not wasteful.

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 describing the return value and does so adequately by listing the kinds of feedback content returned. For a single-parameter read-only tool with full annotation coverage, an agent has enough to call it correctly; only edge-case behavior is missing.

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 description coverage is 100% and the single 'id' parameter is documented in the schema as coming from list_scheduled_posts. The description adds no further semantics about the identifier, so the baseline 3 applies — the schema does all the work.

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 names the specific resource — the feedback conversation attached to a post awaiting approval — and enumerates its contents (client comments, change requests, replies). That is far more concrete than a tautology, though it uses a noun phrase rather than an explicit verb and never distinguishes itself from adjacent siblings like get_mentions or reply_to_post_feedback.

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 phrase 'on a post waiting for approval' implicitly scopes usage to the review/approval workflow, which is useful context. However, there is no explicit when-to-use statement, no prerequisites, and no mention of the obvious companion tool reply_to_post_feedback for responding to the feedback this tool retrieves.

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