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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds context about the nature of the data (public incident status) and examples of included vendors, but provides no additional behavioral details beyond this. It does not contradict 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 single, efficient sentence that is front-loaded with the primary action and resource. It includes illustrative examples without unnecessary detail, earning its place fully.

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 simple, parameterless list tool with readOnly annotations and an output schema, the description provides sufficient context. It names the type of data covered and examples of vendors, making the tool's scope clear without needing extra length.

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?

With zero parameters, the baseline for this dimension is 4. The description does not need to explain parameter semantics, and since the schema has no properties, there is no additional burden on the description.

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 specifies the action ('List') and the resource ('monitored SaaS and infrastructure vendors'), with added context about public incident status data. It distinguishes itself from sibling tools that focus on incidents rather than the vendor list itself.

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 implies usage when a list of monitored vendors is needed, but it does not explicitly state when to use it over sibling tools or provide exclusions. The distinction from get_vendor_incidents is implicit through the focus on vendors, not incidents.

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