mirelo_job_status

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

Describes polling behavior and outputs but does not mention idempotency, rate limits, or auth requirements. Since annotations are absent, more detail would help.

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 succinct sentences conveying endpoint, action, and outputs. No excess information.

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?

Covers key outputs without schema. Could mention polling intervals or multiple calls needed, but sufficient for a simple poll tool.

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?

Parameter description adds context beyond schema (origin from submit-mode response). High schema coverage reduces burden, but description still adds value.

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 the tool polls job status, specifies the endpoint and outputs (progress, success URLs, failure reason). Distinct from sibling submit/preflight/generate tools.

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?

Implies usage after job submission by referencing job_id from submit-mode response. No explicit when-not-to-use, but context is clear given sibling separation.

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