list_watches

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

With no annotations, the description covers cost ('Free') and authentication requirement. For a simple list tool with no side effects, this is adequate transparency. No contradiction with annotations as none exist.

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 two concise sentences, front-loaded with the action. Every word serves a purpose, with no 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?

Given the tool has zero parameters, no output schema, and is a simple list operation, the description fully covers what the agent needs to know: action, scope, auth, and cost. Complete in context.

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 no parameters, so parameter description is not needed. The description does not add any parameter info, but schema coverage is 100%, and baseline for zero parameters is 4.

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 states the tool lists active webhook watches, distinguishing it from create/delete siblings. Uses specific verb 'List' and identifies the resource (watches) and ownership (token).

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 mentions authentication via TENSORFEED_TOKEN and that it's free. Though it doesn't explicitly state when not to use, sibling names imply alternative create/delete tools, providing sufficient context.

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