convergeqa_iterate_status

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

No annotations are provided, so the description carries full burden. It only says 'owner-scoped' without explaining what that means for behavior, side effects, or prerequisites. The tool fetches status, but no details on authentication, rate limits, or error handling are given.

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, which is concise. However, it is under-specified and lacks structure; it does not earn its place by providing sufficient information. A balanced score of 3 reflects acceptable brevity but inadequate content.

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 6 parameters, no output schema, no annotations, and many siblings, the description is extremely incomplete. It fails to explain the tool's scope, return format, or how it relates to other tools. The agent would likely need additional context to use 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 50% (3 of 6 parameters have descriptions), but the required parameter job_id lacks description. The tool's description adds no extra meaning beyond the schema; it does not clarify what job_id represents or how to obtain it. The baseline of 3 due to partial coverage is not improved.

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 'fetch' and the resource 'Iterate job status', indicating it retrieves status information. The term 'owner-scoped' hints at a restriction but is not fully explained. This distinguishes it from some siblings like iterate_start or iterate_decide, but not fully from iterate_session which might also relate to job status.

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?

No guidance on when to use this tool versus alternatives. There are many sibling tools with similar names (e.g., convergeqa_iterate_session, convergeqa_critique_status), but the description does not provide any context for selection or exclusion.

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