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

readOnlyHint=true already tells the agent this is a safe read. The description adds real context beyond that: it checks only what a visitor sees at the project address (home page and its own scripts), and states violations is empty when nothing matches. That scope limitation and empty-result behavior are genuinely useful, though coverage of the broader response shape leans on the output 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?

Purpose is front-loaded in the first clause, the rule enumeration follows compactly, and the deploy-integration note closes it out. Every sentence carries information an agent needs; the parenthetical rule list is dense but justified by the tool's scope.

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 an output schema present, the description need not spell out return fields, and it still covers scope (visitor-visible home page and scripts), empty-result semantics, and when not to bother calling it. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the single 'project' parameter is already documented in detail in the schema (slug, id, or address, with the host-vs-slug caveat). The description adds nothing further about the parameter, so the baseline of 3 applies.

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 ('Check the published site against Layero's anti-phishing rules') and then enumerates the exact rule classes enforced, so it is clearly distinguishable from siblings like check_copy, check_performance and site_issues. An agent knows precisely what this tool inspects.

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?

Explicitly tells the agent that publish_site and site_status run the same check after a deploy and surface rules_warnings only on a match, concluding that a separate call is needed only when the user asks. This gives a clear when-to-use condition and names the alternatives that already cover the case.

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