toast_get_job

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'detailed information' without specifying what details are returned, whether the operation is read-only, or what context is required. The behavior is not misleading, but it is severely underspecified.

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, readable sentence with no filler, so it is concise and front-loaded. However, it is so minimal that it borders on under-specification rather than tight, informative structure.

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 tool with two parameters, no annotations, and no output schema, the description is inadequate. It fails to explain what a 'job position' is in this context, how jobGuid and restaurantGuid should be used, or what the response contains.

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 description coverage is 0%: both jobGuid and restaurantGuid have empty descriptions in the schema, and the tool description mentions neither parameter. The description does nothing to compensate for the lack of information about what each parameter means or how they relate to the job lookup.

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 uses a specific verb and resource ('Get detailed information about a job position'), clearly indicating a read operation for a single job. It contrasts with the sibling toast_list_jobs, though it does not explicitly name or differentiate itself from that sibling.

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?

No guidance is provided about when to use this tool versus toast_list_jobs or other alternatives. The description does not state prerequisites, such as whether restaurantGuid is needed, or when a user should pick this over a list or search tool.

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