get_job

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

No annotations are provided, so the description bears the full responsibility for behavioral disclosure. It only states the basic action and does not mention error handling, permissions, response format, or any special behaviors. For a simple get operation, the lack of additional context is a noticeable gap.

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 conveys the essential purpose without any wasted words. It is appropriately sized for the tool's simplicity.

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 get tool, the description is mostly adequate, but phrases like 'full details' are vague, and there is no mention of what happens when the job does not exist or what the response structure looks like. Since there is no output schema, this lack of specificity leaves some ambiguity.

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 schema has one parameter, 'slug', with no description. The tool description clarifies that the slug is the job's identifier, which adds some meaning beyond the raw schema field. However, it does not explain what a slug is, how to obtain it, or its expected format, so the compensation is minimal.

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 tool's action ('Get'), resource ('full details for a single job'), and identifier ('by its slug'). It distinguishes itself from sibling tools that list or search jobs, making the primary purpose unmistakable.

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 when to use this tool: when you need full details of a single job and you have its slug. It does not explicitly contrast with siblings like search_remote_jobs or list_* tools, but the wording 'single job by its slug' provides clear contextual guidance.

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