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

Adds real behavior beyond the annotations: what is monitored, that only NEW exploited/likely-exploited vulns and new 8-K-flagged SEC filings are reported, and that notify_url triggers autonomous daily Slack/Discord posts. This complements openWorldHint/idempotentHint/destructiveHint rather than repeating them, though it omits auth/tier details beyond the 'PRO' label.

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?

Front-loads the PRO gating and the core action, then layers in reporting behavior and the notify_url option without redundant sentences. Every clause carries distinct information.

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?

With annotations covering safety signals and an output schema handling return values, the description supplies the remaining context an agent needs: what gets watched, what gets reported, and the notification channel. Only edge cases like removing watches or tier limits are left unstated.

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 100%, so all five parameters (manifest, packages, companies, ecosystem, notify_url) are already documented in the schema. The description reinforces purpose but adds little parameter-level syntax or format detail, matching the baseline-3 expectation when the schema does the heavy lifting.

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?

States a specific verb and resource ('Tell Koot what to watch': packages and/or companies), and the additive behavior ('calling again adds to the list') cleanly separates it from the sibling list/unwatch tools (koot_watches, koot_unwatch). An agent can identify its role without opening the schema.

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?

Gives clear context for use ('tell Koot what to watch once') and explicitly describes the accumulation behavior on repeat calls. It stops short of naming when-not or pointing at siblings like koot_unwatch for removal, so it is strong but not fully routing.

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