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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds no further behavioral details (e.g., pagination, sorting order, data limits) beyond stating it returns 'most recently added incidents'. This adds minimal value beyond the annotations.

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 a short phrase, concise but not a full sentence. It is front-loaded but could be more structured (e.g., 'Lists the most recently added incidents.'). It lacks brevity without sacrificing clarity, but is adequate.

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 the simple tool (one optional parameter, output schema exists), the description provides baseline understanding. However, it does not specify default ordering, whether all incidents are included, or how 'recent' is defined (e.g., time frame). Completeness is adequate but not thorough.

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 covers the single 'limit' parameter well, with a clear description of range and default. The tool description does not add additional meaning, so the baseline score of 3 is appropriate. No extra context is provided about how the limit affects results.

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 'Most recently added incidents' clearly identifies the tool as listing recent incidents. The title 'List Recent' supports this. While it distinguishes from siblings like 'search_incidents' and 'get_incident', it could be more explicit about differentiating from other list tools (e.g., 'list_subscriptions').

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 like 'search_incidents' or 'recent_alerts'. The description does not specify context, prerequisites, or when not to use it, leaving the agent to infer usage.

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