get_incidents_today

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

No annotations exist, so the description must fully disclose behavioral traits. It states 'as of snapshot' implying a read operation, but omits details about data freshness, idempotency, permissions required, rate limits, or side effects. The description is insufficient for safe agent action.

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 (5 words) but lacks a complete sentence structure. It could be refined to a full sentence without additional length, improving readability. Currently it is a fragment.

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?

Without an output schema, the description should clearly explain what the tool returns (e.g., incident IDs, severity, timestamps). 'Active incidents across all monitored services' is vague and does not specify the response structure. The tool has no parameters, so the description must compensate, but it fails to do so.

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 input schema has zero parameters, and schema description coverage is 100% (empty). The description does not add parameter-specific meaning, but with no parameters, the baseline is 4. No contradiction or missing info.

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 'Active incidents across all monitored services as of snapshot.' It identifies the tool as returning current incidents, distinct from sibling tools like list_services, get_status, and check_all. However, it is a noun phrase rather than an imperative verb phrase, slightly reducing clarity.

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. There is no mention of prerequisites, when to use, or when to avoid. The agent receives no usage context.

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