get_job

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states 'Get full details' without specifying that it is a read-only operation, any authentication requirements, rate limits, or what happens if the job_id is invalid. The description is insufficiently transparent.

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 sentence of 13 words, front-loaded with the action and resource. Every word is relevant, and there is no redundancy or unnecessary detail.

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?

Given the tool's simplicity (one required parameter, presence of an output schema), the description provides adequate context. It could optionally mention that the output is the full job object, but since an output schema exists, this is acceptable. No information about error cases or performance implications is given, but it is not critical for such a basic 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?

The input schema only provides a string parameter named job_id with no description (0% coverage). The description adds significant meaning by clarifying that job_id can be either a slug or an ID, which helps the agent understand valid inputs beyond the schema's minimal definition.

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 states the action (Get full details), the resource (specific job), and the acceptable inputs (slug or ID). It effectively distinguishes this tool from sibling tools like list_jobs or update_job.

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 description implies usage for retrieving full details of a single job but lacks explicit instructions on when to use versus alternatives such as get_assigned_candidates or list_jobs. No exclusions or when-not-to-use guidance provided.

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