list_upcoming_conferences

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

With no annotations, the description carries the full burden. It discloses that the tool returns upcoming conferences and includes a default 'days' value, adding behavioral context. However, it does not explain return format, ordering, inclusivity of the start/end dates, or pagination, which is a notable gap 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?

The description is a single, front-loaded sentence that states the main action ('List upcoming conferences') and provides the optional parameter context immediately. Every word adds value; there is no redundancy or filler.

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 simple tool with one optional parameter and no output schema, the description covers the core functionality. However, it lacks differentiation from sibling tools and does not describe return details (e.g., which conference fields are included). This makes it adequate 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?

The schema provides no description for the 'days' parameter (0% coverage). The description compensates by explaining that 'days' means 'next N days' and defaults to 60, giving the parameter clear meaning. It does not specify constraints like minimum/maximum or integer requirements, but the core semantics are well covered.

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 clearly states the tool lists upcoming conferences within a time window (next N days) with a default of 60. This provides a specific verb and resource, but does not differentiate it from sibling tools like fetch_conferences and search_conferences, which could overlap in purpose.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies usage for time-based queries but does not explicitly state exclusions or mention other conference-related tools (e.g., search_conferences), leaving the agent without clear selection criteria.

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