get_interviewers_availability_result

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

Without annotations, the description fully discloses the polling lifecycle: status codes (200, 202, 410), TTL (1 hour), and retry advice. It also explains the response slots and how to use them.

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 efficiently structured with a clear first sentence, followed by status details, polling advice, and usage of results. No redundant information.

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 no output schema, the description covers the response content (status, interviewer_ids) and how to apply them in downstream tools. It also addresses edge cases (expiration) and best practices (webhook).

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 single parameter `poll_id` is described in the schema with detail (24-char hex). The description adds no new semantics about the parameter itself, so baseline 3 applies.

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 it polls for the result of a previous `check_interviewers_availability` call, distinguishing it from the parent tool and alternatives like webhooks.

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 provides explicit guidance: when to use (after calling check_interviewers_availability), poll rate (respect Retry-After, not faster than 5s), and when to prefer the webhook for production.

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