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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description usefully adds sort order ('soonest first'), dual time representation (AoE and ISO-8601 UTC), and the default exclusion of projected dates. Missing details like result caps/pagination behavior or data refresh cadence keep it from a 5.

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?

A single dense sentence that front-loads the resource and scope, then qualifies formatting and filtering. No filler, though the final clause about projected dates is somewhat heavy for one sentence.

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 no output schema, the description compensates by disclosing coverage (~64 conferences), ordering, timestamp formats, and default filtering behavior, while all four parameters are bounded or described in the schema. An agent has enough to call this correctly.

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 75% and the area enum, within_days and include_estimated are all documented in the schema. The description only restates the include_estimated filter ('projected (not yet announced) dates are excluded unless include_estimated is true') and says nothing about limit, so it adds little beyond the schema — baseline 3.

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 ('Upcoming paper and abstract deadlines for ~64 ML, CV, NLP... conferences'), plus scope, coverage count and sort order. The plural/list framing cleanly distinguishes it from the singular sibling get_deadline and from list_venues.

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?

Clear context for when this is the right call: upcoming deadlines only, soonest first, projected dates withheld unless include_estimated is true. It does not name an alternative sibling (e.g. get_deadline) or state exclusions in terms of those tools, so it falls short of a 5.

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