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

Annotations already flag openWorldHint=true, readOnlyHint=false and idempotentHint=true; the description adds the crucial nuance that the write is internal only ("Records the result on the app in Vigilia") and that the target site is untouched. It does not cover auth requirements or how often the outbound fetch may be repeated, so it is strong but not exhaustive.

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 short sentences, front-loaded with the action, then the usage condition, then the side-effect boundary. No filler and nothing repeated from the schema or annotations.

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 no output schema, the description should say what the caller gets back from a check. It only says the result is recorded on the app, leaving it ambiguous whether the pass/fail verdict is returned here or must be retrieved via get_app_health.

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?

There is a single required parameter, appId, with 0% schema description coverage, and the description never mentions it. The meaning is largely self-evident from the tool's framing, but the description contributes nothing to disambiguate which app identifier is expected.

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 concrete verb and resource: fetch the live pages and verify both the Vigilia tag's presence and the CSP that permits it to run. That is far more specific than siblings like get_app_health or get_install_instructions, so an agent can tell the three apart without opening schemas.

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?

"Use after deploying an install" gives a clear triggering condition for invocation. It stops short of naming alternatives (e.g. get_app_health) or stating when not to run the check, so it is clear context without explicit exclusions.

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