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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions that platform character limits are enforced, but does not state whether the operation overwrites existing text irreversibly, requires specific permissions, or what happens if the post is not in a pending scheduled state.

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 two short sentences, front-loaded with the primary action. Every word earns its place, with no unnecessary filler or repetition of schema fields.

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 simple two-parameter update operation, the description conveys the core action and a key constraint, but lacks details on return behavior, prerequisites, or error cases. It is adequate but leaves notable gaps given the lack of annotations and output schema.

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 0%, so the description must compensate. It refers to 'text' which maps to the 'content' parameter, giving some hint about its meaning, but does not explicitly explain 'id' or provide format/encoding details. It adds partial value beyond the bare schema.

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 uses a specific verb ('Rewrite') and resource ('pending scheduled post's text'), clearly distinguishing this from sibling tools like create_post or cancel_post. It leaves no ambiguity about the tool's function.

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 'pending scheduled post' clearly delimits when this tool should be used: only for scheduled posts that have not yet gone live. This implies it is not for drafts or published posts, providing clear context without explicitly naming alternatives.

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