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

The description adds no behavioral context beyond the annotations. Annotations already signal it is a non-read-only, non-destructive, non-idempotent operation, but the description does not add details such as side effects, permissions, or calls tied to the required job_id. It merely restates the purpose.

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 concise sentence with no wasted words. It is front-loaded with the action and resource, though it could have used the space to mention that it creates a new offer or reference an alternative without becoming verbose.

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?

The rich schema, annotations, and output schema cover most operational details, so the minimal description is not crippling. However, with 17 parameters and a clear sibling group for offer management, the description omits needed context about creating vs. updating an offer and what 'record' implies for an existing job.

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 100%, and each parameter has its own description in the schema, so the baseline is 3. The phrase 'with compensation details' loosely captures the parameter set but adds no meaning beyond what the schema already provides.

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 states a specific verb ('Record'), a resource ('a job offer'), and a key data area ('with compensation details'). It is clear enough to tell this apart from siblings like jobs.offer.accept or jobs.offer.decline, though it does not explicitly contrast with jobs.offer.update.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this creates a new offer, nor does it reference jobs.offer.update for modifying existing offers, leaving usage context entirely to inference from the tool name and sibling list.

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