art.production.status

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It implies a read-only operation through 'Get', but does not explain what data is returned, what statuses may be observed, whether the tool errors on unknown job IDs, or any side-effect-free guarantees beyond the verb itself.

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 efficient sentence with no filler or repetition. It is front-loaded with the action and resource, though it is so terse that it misses opportunities to add useful routing or behavioral context without becoming verbose.

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 tool with no output schema and no annotations, the description is too thin. It identifies the required parameter but leaves unclear what a caller should expect as a response, what valid production statuses are, and how this tool fits into the production workflow relative to sibling tools.

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?

The schema already describes job_id with 100% coverage as 'Production job ID', so the parameter's meaning is fully documented. The description adds no additional parameter-specific semantics such as ID format, lookup scope, or relation to other production tools.

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 specifies the verb 'Get' and the resource 'current status of a production job', which differentiates it from production lifecycle tools like create, start, resume, cancel, and approve. However, it does not distinguish it from overlapping siblings such as art.production.inspect or art.production.attempts, leaving some ambiguity.

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 is provided about when to use this tool versus alternatives like inspect, attempts, or list. There is no context about polling patterns, prerequisites for a job to have a status, or when another tool would be more appropriate.

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