Describe Job

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral context about job lifecycle and that jobs contain 'status, tasks, metrics, and results', which is beyond the annotation baseline.

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 two short sentences: the first is direct and action-oriented, the second adds necessary context about job creation and content. No fluff or redundancy.

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 one-parameter read-only describe tool with an output schema and annotations, the description is complete enough. It clarifies what a job is, when it exists, and what details are returned. It doesn't cover error cases, but those are less critical given the readOnlyHint and output schema.

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 100%: the only parameter object_id is described in the schema as 'The ID used to retrieve the job'. The tool description adds no extra parameter meaning, so the baseline of 3 applies.

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 opens with 'Get detailed information about a specific job from Itential Platform'—a clear verb+resource pairing. Stating 'specific job' distinguishes it from list-style siblings like get_jobs, and the resource type (job) differentiates it from other describe_* 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?

It explains that jobs are created automatically when workflows execute, providing context for when this tool is relevant. It implies the need for an existing job ID and a one-record lookup, but does not explicitly name alternatives or state when not to use it.

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