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

With no annotations, the description carries the full burden and largely meets it: it discloses the returned payload (full text, recurrence, status detail, comment automation) and the important scheduler-side vs platform-published distinction. It does not cover auth requirements or error behavior (e.g., what happens for a missing/invalid id), which is a modest remaining gap for a read tool.

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 and scope, then the usage routing, then the return contents. Every sentence earns its place; slightly dense but no waste.

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?

No output schema exists, so the description correctly covers return contents (text, recurrence, status, comment automation) and the scope boundary. Only the postId provenance/format and error behavior are left implicit.

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?

One parameter (postId) with 0% schema description coverage, so the description must compensate. It says 'by id' and implies the id originates from list_scheduled_posts, but gives no id format or provenance detail. Adequate, not rich.

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 (fetch) and resource (one scheduler-side post by id) and explicitly scopes it to drafts/queued/recurring/scheduler-published. It also distinguishes itself from two siblings by name (list_scheduled_posts, get_published_media), so an agent can tell exactly what this tool returns versus those.

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?

Explicit when-to-use ('Call AFTER list_scheduled_posts when the user references a specific scheduler entry') and when-not ('For platform-published media use get_published_media'). The alternative and the selection condition are both named.

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