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

Annotations already indicate readOnly=false and destructive=false, and the description adds a useful behavioral constraint: all posts share the same platforms and connection IDs. However, it does not disclose partial-failure behavior, validation limits, or what happens after scheduling is complete.

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 tight sentences with no filler. The core purpose is front-loaded, and the second sentence adds a high-value structural clarification about shared versus per-post inputs.

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 17-parameter tool with many per-platform configs, the description is a solid overview but omits operational context like batch limits, partial failures, or whether scheduled posts can be edited later. The detailed schema and output schema fill many gaps, so this is adequate but not complete.

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%, so the baseline is 3, but the description adds real value by grouping parameters into per-post fields versus shared fields. This helps an agent assemble the correct payload structure without needing to infer the relationship from the large schema alone.

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 states a specific action — 'Schedule multiple posts at once' — and clearly distinguishes this from single-post tools like create_post. It also explains the per-post versus shared parameter model, which makes the tool's scope unambiguous.

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 'multiple posts at once' implies this is the right tool for bulk scheduling, but it never explicitly names alternatives or states when not to use it. An agent must infer that create_post is for single posts and publish_draft is for existing drafts.

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