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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by specifying that this is for a public job and by summarizing the returned content, though it does not discuss failure modes, rate limits, or whether inactive jobs are handled differently.

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 front-loaded, efficient, and free of filler. It states purpose, required inputs, and the sibling-tool relationship in three short sentences.

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 two required parameters, 100% schema description coverage, read-only/open-world annotations, and an output schema, the description supplies everything an agent needs to select and invoke the tool correctly.

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 baseline is 3. The description adds provenance beyond the schema by explaining that the token and id come from jobs_greenhouse_board, which helps an agent understand how to populate the required parameters correctly.

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 gives a precise verb and resource: 'Fetch details for one public Greenhouse job.' It states exactly what content is retrieved (description, requirements, qualifications, application URL) and explicitly distinguishes this tool from jobs_greenhouse_board.

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 names the alternative tool explicitly and gives the condition: use jobs_greenhouse_board to list openings, while this tool retrieves one posting. It also tells the agent where to obtain the required token and id.

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