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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that interviews are detected from email confirmations and clarifies the semantics of upcoming=true, but it does not mention return format, pagination behavior, or any other operational details. Some useful context is added, but not comprehensive.

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 two sentences, front-loaded with the core purpose, and each clause adds value. It is efficiently worded without redundancy, making it easy to parse quickly.

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 list tool with five optional parameters and no output schema, the description covers the core purpose, data source, and filtering semantics. It does not describe return values, but the tool name and list-oriented nature make this less critical. The absence of pagination details is mitigated by well-documented schema fields.

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 coverage is 100%, so a baseline of 3 applies. The description adds meaning by explaining that upcoming=true returns scheduled/rescheduled interviews (matching the enum values for those statuses) and by summarizing filtering by application ID or status, going beyond a simple restatement of parameter names.

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 uses a specific verb ('List') and resource ('job interviews'), and clarifies the scope ('actively tracked by JobGPT'). It distinguishes this tool from sibling list tools by explaining the data source (email confirmations), making its purpose unambiguous.

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 provides clear usage context, explaining how to get scheduled/rescheduled interviews with upcoming=true and mentioning additional filters by application ID or status. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to decide when to use this tool.

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