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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get one,' implying a read operation, but does not confirm idempotency, rate limits, or any side effects, leaving the agent uninformed about safety.

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 short with two sentences, avoiding excessive detail. However, the second sentence is somewhat ambiguous ('for opening inventory and owner analysis') and could be more precise.

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 five parameters, including nested objects and an enum, the description is too brief. It does not explain the use of 'include', 'query_json', or 'path_params', nor does it describe the return value or error cases, leaving significant gaps.

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?

The input schema already describes 80% of the parameters (including id, query_json, detail_profile). The description adds no extra meaning to parameters; thus it meets the baseline but does not enhance understanding.

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 clearly states the tool retrieves a single opening_offer and clarifies that these are jobs or talent pools. However, it does not mention the required 'id' parameter explicitly, which is essential for specifying which offer to fetch.

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 phrase 'Get one' implies a contrast with list operations like list_opening_offers, but there is no explicit guidance on when to use this tool versus siblings, nor any conditions or exclusions.

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