Update Scheduled Post

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

No annotations provided, so the description bears full burden. It mentions two constraints but does not disclose potential side effects, required permissions, or whether the operation is reversible. For a mutation tool, more behavioral context is needed.

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 purpose, and each sentence adds value. No redundant or vague phrasing.

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. The tool has 11 parameters with nested objects. The description is too brief; it lacks information about return values, error conditions, or effects of updates on dependent data. More context is needed for a tool of this complexity.

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 55%. The description adds high-level meaning ('the account cannot be changed; provide the new content fields') and specifies the scheduleAt format, but does not detail the other 9 parameters. The schema already covers some, but the description could add more context.

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?

Clearly states the verb 'update' and the resource 'existing scheduled post'. Distinguishes from sibling create_schedule (new) and get_schedule (read). The description uniquely identifies the tool's purpose.

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?

Explicitly notes that the account cannot be changed and that scheduleAt must be a future ISO 8601 timestamp. While it doesn't name alternatives, the constraints provide clear guidance on when to use this tool.

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