get_job_status

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Read' and 'without executing it again' clearly signal a non-mutating status operation, but the description does not mention permissions, error behavior, or state-transition effects.

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 front-loaded sentence that states the verb, resource, and a meaningful qualifier without any filler. Every word earns its place.

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 do not need to be described, and the non-execution qualifier adds useful safety context. However, the description omits parameter semantics and fails to disambiguate this tool from get_sdg_job_status or get_motion_status, leaving significant gaps for correct selection and invocation.

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 description provides no explanation of job_id, command_id, or idempotency_key. The agent receives no semantic guidance beyond the parameter names in the schema.

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 uses a specific verb ('Read') and names its resource ('managed, motion, or SDG job') while explicitly noting it does not re-execute the job. This makes the core purpose clear, though it does not explain how it differs from the specialized sibling tools get_sdg_job_status and get_motion_status.

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 phrase 'without executing it again' implies this is for inspecting an existing job rather than launching one, which provides some usage context. However, there are no explicit when-to-use instructions, exclusions, or references to alternative tools, so an agent must infer the right choice.

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