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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing what the call surfaces (home view, per-monitor state and last check, latest changes with screenshots), which is not derivable from the empty schema. It stops short of noting result limits or pagination for the changes list, so it is strong rather than complete.

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: the first front-loads the outcome and enumerates the contents, the second carries usage and the alternative. Every clause earns its place — the content list is what lets the agent decide between this and a report tool.

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 input parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so at a useful level of detail (monitors, states, last check, changes with screenshots). Minor gaps remain around volume/recency of the changes list and whether the "home" framing implies any UI side effect, but nothing essential to invoking it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly signals a no-argument, take-me-to-the-overview call by describing it as opening the user's home rather than accepting filters.

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 ("Show") and a concrete resource ("the pages the user watches and what changed on them"), then enumerates the payload: monitor state, last check, and latest changes with screenshots. It also names the sibling get_recent_changes as the contrasting tool, so an agent can distinguish it from list_monitors/get_recent_changes without opening any 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 an explicit positive condition ("when the user wants an overview of what they watch or to browse changes") and an explicit negative/alternative routing rule ("for a written report use get_recent_changes"). This is exactly the when-to-use/when-to-use-something-else guidance an agent needs.

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