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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the description is free to add what structured fields can't: that the page is rescored on every monthly run, that it consumes the plan's page allowance, and that it returns updated monitor state. These quota and repeat-scoring behaviors are the kind of context annotations don't carry.

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-loaded with the purpose and cadence, then quota, then return value and endpoint. Dense but each sentence carries distinct information; the API reference URL is the only slightly expendable element.

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?

No output schema exists, yet the description covers the return value ('updated monitor state'), the side effect (counts against page allowance), the trigger cadence, and the underlying endpoint. For a 3-param mutation with annotations already handling safety, an agent has what it needs to call this correctly.

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 67% and the description adds little per-parameter meaning: 'against a profile' loosely maps to profile_id (which has no schema description) and 'public page' restates the url constraint the schema already documents. The 'label' parameter is never addressed, so it does not compensate for the coverage gap.

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+resource+scope: 'watch a public page for voice drift against a profile'. The parenthetical about running on every monthly run and on run_voice_monitor implicitly separates it from the sibling that performs the run, so an agent can distinguish add_monitor_url from remove_monitor_url and run_voice_monitor.

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 concrete usage context ('the about page, pricing, recent posts, anywhere the voice is published') and clarifies the ongoing cadence (monthly run/run_voice_monitor). It stops short of stating when NOT to use it or explicitly naming remove_monitor_url as the counterpart for undoing the watch.

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