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

No annotations provided; description partially discloses output fields (firstSeenAt, ledgerVerified) but omits behavioral traits like read-only nature, side effects, or rate limits. Minimal transparency beyond schema.

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?

Two sentences: first states purpose concisely, second describes output fields. No redundant information, efficiently front-loaded.

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 3 parameters, no output schema, and no annotations, the description is too brief. It omits parameter details, pagination hints, and clarification of output fields, leaving gaps for effective use.

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?

Schema description coverage is 0%. The description only implicitly references the 'since' parameter but does not explain 'limit' or 'vendor'. No additional meaning beyond the schema.

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 the tool retrieves recent revised events across SaaS ToS documents since a timestamp, which is clear and distinguishes from sibling tools like tos_watch_get or tos_watch_search. However, it lacks an explicit verb (e.g., 'retrieve'), relying on context.

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 on when to use this tool versus alternatives (e.g., tos_watch_search, tos_watch_timeline). The description does not mention when-not or preferability conditions.

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