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

With no annotations, the description carries the burden. It adds useful context ('active', 'last known scores and check times', 'Unmetered') but does not disclose authentication needs, rate limits beyond unmetered, or error/empty-list behavior. It gives a moderate level of transparency, not comprehensive.

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 concise sentence that front-loads the verb and resource, then adds the output fields and an 'Unmetered' note. Every word earns its place; no fluff or redundancy.

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 0-param list tool with no output schema, the description adequately explains what is returned and the unmetered nature. It lacks details on pagination or empty results, but given the low complexity, it is sufficiently complete. A small gap remains around ordering or potential large data, so not a full 5.

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 tool has zero parameters, which sets a baseline of 4. The description adds no parameter details (none are needed) but does clarify the license scope, which is a contextual bonus. No gaps exist since there are no parameters to describe.

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 opens with the specific verb 'List' and names the resource: 'active site watches' with 'last known scores and check times.' This clearly distinguishes it from siblings like watch_site and unwatch_site, which perform different actions.

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 gives clear context by scoping to 'this license's active site watches' and indicating a list operation. While it does not explicitly name alternatives or when-not-to-use conditions, the activity is self-evident and complements sibling tools that create or remove watches.

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