civil3d_status

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

With no annotations, the description must convey behavioral traits. It notes the tool is non-blocking ('without blocking the current operation'), implying a read-only status check. However, it omits details like error handling or that it doesn't modify data, leaving some gaps.

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 two sentences, front-loads the purpose and usage, and contains no redundant information. Every sentence serves a clear role.

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?

While the description explains what the tool does and when to use it, it lacks details on the return value (e.g., format, fields like queue length or task name). Without an output schema, the description should elaborate on the output structure.

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?

There are zero parameters, so the description does not need to add parameter details. Schema coverage is 100% (all parameters documented), and the baseline for 0 parameters is 4, which 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 tool retrieves 'real-time status of the Civil 3D plugin operation queue and any in-progress task,' using a specific verb and resource. It distinguishes from siblings like civil3d_health and civil3d_execute by focusing on status monitoring rather than diagnostics or actions.

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 explicitly advises using the tool 'during long operations (corridor rebuild, surface build) to check elapsed time without blocking the current operation,' providing clear context. It does not mention when not to use it or list alternatives, but the implied use case is sufficient.

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