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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds only 'with full description', implying a detail payload, but says nothing about auth requirements, rate limits, or how much data is returned beyond what the output schema carries.

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?

It is a single short phrase with no filler, so it is concise and front-loaded. However, that brevity comes at the cost of substance rather than from tight editing of rich content.

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?

An output schema exists, so return values need not be described. But for a two-parameter lookup tool, the definition leaves both parameters undocumented, gives no usage routing against the sibling list tool, and offers no behavioral context, making it too thin to call correctly from the text alone.

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% for both required parameters (id, company), and the description does not explain what 'id' refers to or what 'company' expects. With zero schema documentation, the description should compensate but does not.

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 names the resource ('Recruitee offer') and its scope ('Single ... with full description'), which implicitly distinguishes it from the plural sibling jobs_recruitee_offers. However, it is a noun fragment with no verb, so the actual action (fetch/retrieve a detail record) must be inferred.

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?

There is no indication of when to use this tool versus jobs_recruitee_offers or any other sibling. The word 'Single' weakly hints at detail-vs-list usage, but no explicit guidance, prerequisites, or exclusions are provided.

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