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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that each entry carries a running/paused state and that the monetary fields are UTC-calendar-month maxima, which is genuine behavioral context. It says nothing about result size, ordering, or pagination behavior, which matters for a list operation.

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, front-loaded with purpose, with no filler or repetition. But the second sentence is dense field-definition prose about output fields while the pagination and scoping parameters that determine the call itself go entirely unmentioned, so the space is spent on the wrong details.

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?

There is no output schema, so the description does helpfully define the two monetary fields. But an agent still cannot determine how to paginate, what 'after' expects, or what limit defaults to, which are essential for calling a paged list tool correctly. The monitor-versus-capacity-schedule terminology gap is also left unresolved.

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?

All three parameters (after, limit, project_id) have zero schema description coverage and the description never mentions them. It does not explain that 'after' is a pagination cursor, that 'limit' caps at 100, or that project_id narrows results to a project. For a low-coverage schema the description carries the burden and fails to.

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?

The first sentence gives a specific verb and resource: 'Lists the account's monitors and whether each is running or paused.' An agent can tell this is a read of monitor state. However, the tool name says 'capacity_schedules' while the description and title say 'monitors', and the description never bridges the two terms or points to the related capacity-schedule siblings (create/update_capacity_schedule, list_capacity_occurrences).

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?

There is no guidance on when to call this versus alternatives such as list_capacity_occurrences or get_capacity_entitlements, and no prerequisites or scoping advice. The only contextual hook is 'the account's', which implicitly scopes the result but does not tell the agent when this tool is the right choice.

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