lunaar_get_operation

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

No annotations provided. Description indicates a read operation ('inspect') but does not disclose potential traits such as rate limits, authentication needs, or response format. For a simple get by ID, the transparency is adequate but minimal.

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 concise sentences, no unnecessary words, front-loaded with the primary action.

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 get operation with no output schema, the description covers the core purpose and usage. Minor gap: does not explicitly describe the return value, but the context of polling implies status information.

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 0% for the only parameter (operationId). The description does not elaborate on the parameter beyond its name. While the name is self-explanatory, with 0% coverage, the description should offer more detail. Baseline for 0% is low, but 1 param prevents a 1.

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?

Clearly states 'Inspect any operation by id', which is a specific verb and resource. Distinguishes from sibling lunaar_list_operations which lists operations, and mentions a specific use case (Image-to-3D run).

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?

Explicitly specifies when to use: 'when an earlier tool returned a non-terminal status, or to poll a long-running Image-to-3D run'. Provides clear context and implies not for other purposes.

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