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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety profile is covered. The description adds that it lists 'most recent' and includes 'results and remaining credit balance', but does not explain pagination, ordering, or response format details beyond that.

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?

A single sentence that is front-loaded, information-dense, and contains no unnecessary words. It efficiently conveys purpose, scope, and return content.

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 read-only annotations, simple schema, and no output schema, the description is nearly complete. It covers what is listed and what is returned. A small gap is missing how many defaults (though schema says default 10) or any ordering details, but overall sufficient for an agent to invoke correctly.

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 the schema fully documents the only parameter 'limit' with description. The tool description does not add any parameter semantics beyond what's in the schema, so baseline 3 is appropriate.

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 states a specific verb 'List' and resource 'screenings', clarifies scope 'on the account that owns the API key', and mentions returns 'results and remaining credit balance'. This distinguishes it from siblings like get_screening (single) and screen_audio (create).

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?

Implies usage for listing recent screenings but does not explicitly state when to use this vs. get_screening or screen_audio. However, the scope is clear enough for an agent to infer it's for listing recent items, not fetching a specific one or creating a new screening.

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