list_interviews

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

With no annotations, the description transparently discloses that cancelled interviews are included by default and that filters are rich. It does not mention authentication, rate limits, or performance, but the core behavior of listing is well-described. The default inclusion of cancelled interviews is a notable trait beyond basic filtering.

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?

Two sentences: the first states the main purpose, the second summarizes filters and the default behavior tip. It is extremely concise, front-loaded, and every sentence adds value. No wasted words.

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 22 parameters and no output schema, the description covers the essential: account-wide listing, rich filters, and the default inclusion of cancelled interviews. It lacks mention of pagination or output format, but the schema already describes pagination params. Overall, it is sufficiently complete for a listing tool.

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?

Since schema coverage is 100%, the baseline is 3. The description adds a summary of filter dimensions but does not provide additional meaning beyond what the schema's parameter descriptions already offer. The summary helps quick understanding but does not significantly enhance parameter semantics.

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 lists interviews for the account, using a specific verb and resource. It distinguishes itself from sibling tools like get_interview (single) and list_application_interviews (scoped) by emphasizing account-wide scope and rich multi-value filters.

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 gives a clear usage tip about cancelled interviews being included by default and how to filter them. However, it does not explicitly contrast with list_application_interviews or other sibling tools, leaving some ambiguity about when to use this vs. the scoped variant.

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