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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is low; the description still adds the required scope 'database:read' and, importantly, the shape of each returned item — which matters because there is no output schema. It does not mention pagination, ordering, or limits, which is the one remaining gap.

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 short sentences, the resource and its scope front-loaded, then the returned fields and the permission scope. No filler or restated title.

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 zero-required-parameter read tool with full schema coverage and complete annotations, the description covers return fields and required scope, so an agent can call it correctly. Only ordering/pagination and explicit sibling routing are absent, which keeps it below full marks.

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 100%, and the schema itself documents all three optional parameters with their defaulting rules (production, last-used project, token's org). The description only echoes the branch scoping ('The branch's…') and adds no extra meaning, so baseline 3 applies.

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 description gives a specific verb+resource ('The branch's scheduled jobs (pg_cron)') and enumerates the returned columns (name, schedule, target, active, last run). It implicitly distinguishes itself from schedule.runs and schedule.create/update/delete by being the plain listing, but never names those siblings explicitly.

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 when-to-use guidance and no exclusion of alternatives. An agent must infer that this lists definitions rather than run history (schedule.runs) or that schedule.create is the write counterpart. The scope note hints at permissions but is not a usage rule.

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