fetch_offer

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

Discloses headless browser rendering, which is useful. However, with no annotations, more details about output format or potential limitations would improve transparency.

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?

Concise and well-structured: purpose first, then usage, then technical note, then parameter. Every sentence is essential.

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?

Covers main aspects: purpose, usage context, technical details. With an output schema present, the description is sufficiently complete for a simple fetch 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?

Only one parameter (url) described as 'the job offer URL', which adds minimal value over the schema's type string. With 0% schema coverage, the description should elaborate on expected format or examples.

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?

Clearly states the action 'Fetch a job offer' from a URL, returning visible text. Distinct from sibling tools like generate_letter_pdf and load_cv.

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 says 'Use this when the user gives a link instead of pasting the offer', providing clear context. Also notes it works on JavaScript-heavy job boards, aiding selection.

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