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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the target must already exist, is scheduler-side, and rejects published/publishing states. It also discloses first-call naming behavior devoteesfully, though it does not mention side effects or whether omitted fields are preserved.

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?

The description is front-loaded with the core action and scoping, and each added detail—examples, first-call rule, rejection of published states—serves a clear operational purpose. It is somewhat dense and repetitive around the RESCHEDULE distinction, but not bloated.

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 tool with no annotations and no output schema, this description gives substantial context: state constraints, exclusions, identification strategy, and editable fields. Minor gaps remain, such as no exact scheduledAt formatament and no mention of postId, but the essential calling behavior is well covered.

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 0%, so the description must compensate for the schema's silence. It explains postName as the display/caption used for identificationable and scheduledAt as a user-provided time expression. However, postId is never mentioned, and exact formats for scheduledAt and timezone are left unspecified, leaving partial coverage.

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 verb and resource: 'Edit a scheduler-side post that ALREADY EXISTS (draft or scheduled) — text, time, timezone.' It differentiates itself from scheduling tools via 'RESCHEDULE always means this tool, never schedule_post' and from creation tools via 'ALREADY EXISTS.'

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?

It gives explicit when-to-use guidance: reschedule or move an existing draft/scheduled post, with natural-language examples. It excludes alternatives ('never schedule_post'), forbids listing posts first, and clarifies the scheduler-side vs platform-published scope.

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