get_job

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

Annotations already declare the tool as read-only, non-destructive, and non-open-world, so the description needn't repeat safety. The description adds that it fetches 'public description and details' of a 'visible job', implying access controls, but doesn't specify error cases or rate limits. With annotations covering basics, a 3 is appropriate.

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?

Two sentences, zero waste, and front-loaded with purpose followed by usage condition. 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?

Given the tool's simplicity (one parameter, output schema present), the description provides all necessary context: what it does, when to use it, and the scope. Annotations cover safety, and output schema handles return values, so nothing critical is missing.

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%, so the single parameter 'id' is fully described. The description doesn't add format or semantics beyond 'by ID', which is redundant with the schema. Baseline 3 is correct when schema is complete.

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 a specific verb ('Fetch') and resource ('full public description and details of one visible job by ID'). It distinguishes from 'search_jobs' (bulk search) and 'get_jobs' (probably listing), allowing an agent to select the correct tool without opening schemas.

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?

Explicitly states when to use this tool: 'Use after search_jobs when the complete vacancy is needed.' This provides both the trigger (post-search) and the condition (full details required). Sibling tools are indirectly referenced, giving clear context.

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