list_valid_organizers

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

The description discloses eligibility criteria but does not mention pagination behavior, output format, or any side effects. With no annotations, the description carries full burden; it is somewhat transparent but lacks detail.

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 sentence that immediately states the purpose and criteria. No unnecessary words, well front-loaded.

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 description covers the purpose and eligibility but lacks details on pagination parameters, output structure, and potential limitations. For a tool with no output schema and no annotations, it is incomplete.

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 description only adds context to job_id by explaining its role. It does not explain page or limit parameters, which have no descriptions in the schema. With 50% schema coverage, the description fails to compensate for missing parameter meanings.

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 verb 'List' and the specific resource: users eligible to be organizer_id for interview scheduling. It distinguishes from sibling tools by specifying eligibility criteria (connected calendar and permission).

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 implicitly indicates when to use this tool (when needing an organizer_id for an interview). No alternatives are mentioned, but given the sibling list, no direct alternative exists, so the guidance is adequate.

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