update_post

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 transparency. It states that the tool updates a post, indicating mutation, but fails to disclose important details such as required permissions, side effects (e.g., whether it can update published posts), or whether changes are reversible. This lack of context leaves the agent uncertain about the tool's full behavioral implications.

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 a single short sentence that efficiently conveys the core purpose. It is front-loaded and contains no unnecessary words.

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?

Given the tool has 3 parameters (100% schema coverage) and no output schema or annotations, the description covers the basic functionality but lacks context on when to use, what happens if a post is already published, and expected return values. The completeness is adequate but not thorough for a mutation tool.

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?

The input schema has 100% coverage, so the baseline is 3. The description adds minimal value beyond the schema: it repeats the status values (draft/scheduled) and mentions scheduled time, but provides no additional details on formatting, constraints, or relationships between parameters.

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 clearly states the verb 'Update' and the resource 'post', and specifies what can be updated: status (draft/scheduled) or scheduled time. This distinguishes it from sibling tools like create_post, delete_post, and get_post.

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 description implies the tool is used to change a post's status or scheduled time, but it does not provide explicit guidance on when to use it versus alternatives (e.g., create_post for initial creation or delete_post for removal). No context on prerequisites or situations to avoid.

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