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

Goes well beyond the annotations (idempotent, non-destructive) by disclosing that content is preserved, that alerts cease, quota accounting changes, and the exact error code returned when the limit is exceeded. This is exactly the side-effect detail an agent needs before toggling.

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 tight sentences with the toggle semantics front-loaded, followed by consequences. The trailing response-shape line duplicates the existing output schema and is the one piece of avoidable content.

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?

For a two-parameter idempotent toggle with annotations and an output schema, this covers effects, quota behavior, and failure mode. The redundant response enumeration adds nothing beyond the output schema, and prerequisites (auth/permissions) are unmentioned.

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 50% and the undocumented parameter (monitoring) is precisely the one the description explains — false vs true semantics plus consequences. list_name is covered by the schema pointer to list_watched_companies; the description could restate that requirement but the gap is minor.

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 (enable/disable) and resource (monitoring on a list), with the boolean value mapping spelled out. It doesn't explicitly contrast with siblings like watch_company/unwatch_company, so an agent must infer that this targets saved lists rather than individual companies.

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 clear operational context: disabling stops alerts and exempts the list from the watched-company cap, re-enabling counts the whole list and can fail with watch_limit_reached. It stops short of explicitly naming when to prefer watch_company vs this list-level toggle.

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