Check Multiple Blog Workflow Statuses

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

Annotations already indicate readOnlyHint and destructiveHint. The description adds that it polls, provides a rollup status, and returns per-item results identical to check_blog_status. This goes beyond annotations with useful behavioral context.

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: first states core function and limit, second describes return structure. No fluff, front-loaded, efficient.

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 batch polling tool with full schema coverage, annotations, and a clear output description, the description covers all necessary context. Output schema is omitted but the description explains the return shape adequately.

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 100% with workflow_ids described as 'Up to 25 blog workflow_ids to check'. The description repeats 'up to 25 blog-creation workflows' without adding new parameter details. 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 clearly states the verb 'Poll' and the resource 'blog-creation workflows' and specifies the batch size limit. It distinguishes from siblings like check_blog_status and other batch_* tools by indicating a rollup and per-item array.

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 use for multiple workflows but does not explicitly state when not to use or provide alternatives. It references check_blog_status for shape but lacks direct comparison to other batch tools like batch_check_page_status.

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