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

With no annotations provided, the description must carry the behavioral burden. It discloses pagination behavior ('Paginated (default page 1, limit 20)'), which is useful, and implies read-only operation via 'List'. However, it does not disclose whether the operation is safe, idempotent, or has any side effects. Since annotations are absent, a 3 is appropriate for including some behavioral context but missing deeper transparency like rate limits or error cases.

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 covers purpose and filters; the second covers pagination defaults. No fluff, every word earns its place, and the critical action is front-loaded. This is a model of conciseness.

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 endpoint with no output schema and no annotations, the description covers essential aspects: purpose, filters, and pagination defaults. It does not describe the return structure (e.g., array of jobs with fields), but given the tool's simplicity and the schema's completeness, it is nearly complete. Could mention that the response includes total count or that filters are optional, but these are minor gaps. Thus a 4 is justified.

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 schema provides 100% coverage of all parameters with clear descriptions (e.g., 'ISO timestamp' for since/until, enum for status). The description only mentions 'filters for status and time range', which adds minimal value beyond the schema. Baseline 3 is correct as the description does not contradict or significantly enhance parameter understanding.

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 action ('List transcode jobs'), the target resource (transcode jobs for the authenticated account), and the optional filters. It distinguishes itself from sibling 'get_transcode' (which likely retrieves a single job) by implying a list operation. The verb 'List' and resource are specific and 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 context on when to use (listing jobs with optional filters) but does not explicitly state when not to use it or suggest alternatives like 'get_transcode' for retrieving a specific job. The filters (status, time range) imply typical usage scenarios, but there is no direct comparison with sibling tools. This is a clear but not proactive usage guideline.

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