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

Beyond the annotations, it discloses that reports are not published and instead influence what Botworthy scans or rescans next, clarifying the downstream side effect. It also supplies substantive privacy and eligibility constraints, all consistent with the non-read-only, non-destructive 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?

Three compact sentences front-load the purpose, then explain the downstream effect, and finish with eligibility and privacy restrictions. Every sentence contributes useful information without filler or unnecessary repetition of the schema.

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?

Together with the detailed schema, the description provides enough context to construct a compliant report and understand why it is submitted. It remains short of fully complete because sibling-tool routing, outcome-selection criteria, and acceptance or error behavior are not explained, and there is no output schema to supply response details.

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 78% schema coverage, the schema already documents most fields, including the nested steps and followedRules structures. The description adds a valuable cross-field prohibition on user information, but does not clarify reporting conventions such as when outcome should be partial versus failed or blocked.

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 opening sentence clearly states that the tool reports to Botworthy how one of five supported tasks went on a website. It provides some post-visit context through the scanning explanation, but does not explicitly distinguish the tool from check_site or request_scan.

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?

It gives strong when and when-not guidance: report a performed task only if the visit involved no login, personal-data entry, or CAPTCHA/bot-check bypass, and never include user information. Explicit routing to check_site or request_scan for related needs would make tool selection more complete.

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