get_job

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

Annotations already declare readOnlyHint=true, and 'Return' is consistent with a read operation. The description adds only the 'current' freshness nuance and the metadata/status scope, but does not disclose behavior like caching, error handling, or auth requirements. With the annotation covering the safety profile, this 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?

A single, short declarative sentence with no redundancy. Every word contributes to the meaning, and the key scope ('one job') is front-loaded.

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, single-parameter, read-only tool with an output schema and readOnlyHint annotation, the description doesn't need to explain return values. It covers what the call does and at what scope, but the lack of sibling routing guidance keeps it from being fully complete.

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 is one parameter, job_id, and the description maps to it indirectly via 'for one job'. Schema description coverage is 0%, so the description should compensate; it partially does by clarifying the target of the operation, but it does not explain valid formats, how to obtain a job_id, or edge cases.

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?

Description states a specific verb and resource: 'Return' plus 'one job', and specifies the content as 'current metadata and status'. This makes the operation clear and distinguishes it from sibling plural/result tools like get_jobs and get_results.

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 'for one job' implies when to use it, but no explicit alternatives or exclusions are given. An agent gets no direct guidance on choosing between get_job, get_jobs, list_jobs, or get_result.

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