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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description only needs to add beyond that. It does add two useful traits: the default sort ('newest first') and the per-item return contents ('schedule and next_fire_at'), which is valuable since no output schema exists. Pagination behavior is left unmentioned.

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, zero filler, and the most decision-relevant facts (what is listed, default ordering, filter axes, returned fields) are front-loaded in that order.

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 9 parameters and no output schema, the description usefully covers what each item contains, which is the main gap an agent would otherwise face. It stops short of mentioning pagination/cursor usage or result counts, so it is strong but not fully complete.

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 description coverage is 100%, so every parameter is already documented in the schema; the description's list of filter dimensions maps onto name, agent_id, agent_profile_id and integration_id but adds no syntax or format detail beyond them. Baseline 3 is appropriate when the schema carries the semantics.

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 and resource ('Lists the project's cron triggers') plus scope, default ordering, and the dimensions it can be filtered by, which is enough to separate it from crons_get and crons_create. It does not explicitly name a sibling alternative, so it falls short of the top band.

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?

'filterable by name, agent, profile, or integration' implies when the tool is useful, and 'newest first by default' hints at the default behavior, but there is no explicit when-to-use versus crons_get or any stated prerequisite for the required orgID/projectID. Usage is left to inference.

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