list_annotations

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

No annotations exist, so the description must fully disclose behavior. It only mentions ordering (newest first) and date range scope, but omits information on pagination, limits, or what exactly is returned (e.g., all annotations or just those in range).

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 extremely concise, but it is not a complete sentence and lacks structure. It efficiently conveys ordering and scope, but the brevity borders on underspecification.

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 no output schema and no annotations, the description should explain return values or provide more context. It fails to describe what the tool returns beyond 'annotations', and it does not clarify parameter details or usage constraints.

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 implies a date range parameter, but the input schema has no defined parameters (only additionalProperties: true). This creates a mismatch: the description suggests parameters that are not documented in the schema, potentially confusing an AI agent.

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 'Annotations in a date range, newest first' is a noun phrase without a verb, making it unclear that the tool lists annotations. It does not specify the action (list, get, etc.) and is ambiguous compared to siblings like get_annotation or add_annotation.

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?

No guidance is provided on when to use this tool versus alternatives such as get_annotation for a single annotation or other list tools. The description offers no context for selection.

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