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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is low; the description usefully adds result ordering, a hard cap of 20 rows per call, and how to page. The paging instruction says 'next_offset' while the schema exposes an `offset` parameter, which will confuse an agent trying to paginate.

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?

Three short sentences, front-loaded with purpose then filters then result limits; nothing is padded. The final clause is slightly wasted because it references a parameter name ('next_offset') that does not exist in the schema.

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 an output schema present, return values need no explanation; the description covers ordering, page size ceiling and pagination, which is what an agent needs before calling. The only loose end is the mismatched pagination parameter name.

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 83% and every parameter carries its own description with format examples, so baseline is 3. The description only restates the field/category/date filters and adds nothing about the format or defaults of `after`, `before`, `limit` or `offset`.

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 plus scope: 'List open and announced public submission deadlines in date order.' That is clearly distinct from list_calendars and fetch, though it never says how it differs from the sibling `search`.

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?

Names the available filters (field, category, date range) and the pagination mechanism, which implies the intended listing use case. It gives no explicit when-to-use versus `search` or `list_calendars`, and no exclusions or prerequisites.

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