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

Beyond the annotations, the description discloses meaningful behavioral details: the post is queued for all target channels, requires a specific permission, returns 403 APPROVAL_REQUIRED for contributors, and implicitly approves pending/rejected posts when an approver publishes. No annotation contradiction is present.

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 four sentences long, front-loaded with the primary action, and every remaining sentence adds essential context—permission requirements, alternative workflow, and implicit approval behavior. There is no 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 single-parameter tool without an output schema, the description fully covers when to use it, what happens on success, permission constraints, error behavior, and the alternative approval flow. No additional context is needed for an agent to invoke it correctly.

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 100%: the only parameter, postId, is already documented as 'The post ID to publish.' The description reinforces that the post must be an existing draft or scheduled post, but this adds limited new meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Publish a draft or scheduled post immediately.' It clearly distinguishes this from sibling tools like create_post, update_post, and publish_story by scoping it to existing posts that need immediate publication.

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 explicitly states when to use the tool ('when the user wants to publish an existing draft or scheduled post right now') and gives an alternative path for contributors lacking post:publish permission, routing them to create/update with requestApproval and a teammate approval. This directly addresses when-not-to-use and the correct alternative.

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