Batch collection status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description usefully adds that the run state is durable and survives client exit. It does not explain why a pure status read carries idempotentHint=false, nor does it describe polling expectations or rate limits. Some added context, but the odd annotation is left unexplained.

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?

A single front-loaded sentence with zero filler. The key qualifier (durable, post-exit) is placed immediately after the verb and resource.

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?

An output schema exists, so return values need no explanation, and one parameter keeps the surface small. Still missing is the provenance/semantics of run_id and any statement of how this relates to revit_batch_start, revit_batch_fetch and revit_batch_cancel in a batch workflow.

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% and the single required run_id parameter is never mentioned in the description. An agent gets no hint that run_id comes from revit_batch_start or how it is formatted, so the description fails to compensate for the coverage gap.

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?

States a specific verb (Read) and resource (durable run and model status), which is clearly distinct from revit_batch_start, revit_batch_cancel and revit_batch_fetch. It does not explicitly name those siblings or state the boundary between status polling and result fetching, so it stops short of a 5.

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?

"After the initiating client exits" gives a genuine timing condition for use, implying polling of a long-running batch. However, it never names the alternatives (revit_batch_fetch for results, revit_batch_cancel to abort, revit_jobs for job listings) or states when this is not the right call, so usage is only implied.

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