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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its budget elsewhere: newest-first ordering, a 50-item cap with total count, and the company's conferencedatabase.com page. That pagination/sort behavior is exactly the kind of trait annotations cannot express.

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?

Front-loaded with the usage trigger, then the input format, then the return shape, with no filler. It is slightly long for a two-parameter read tool, but each sentence carries information.

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?

An output schema exists and annotations cover safety, so the remaining burden is just telling the agent when to reach for this tool and what shape of question it answers — both present. Nothing needed to call it correctly is missing.

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%, so both parameters are already documented, including the 'Salesforce'/'salesforce.com' example the description repeats. The description adds no new semantics for upcoming_only or the maxLength constraint, so the 3 baseline is correct.

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+resource ('get the conferences a company sponsors or exhibits at') and adds the forward-looking angle ('or where it will be next'). An agent can distinguish this from get_conference, get_conference_sponsors, and search_conferences because the lookup is anchored on a company rather than a conference.

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?

'Use this when someone asks which conferences or trade shows a company sponsors or exhibits at' gives an explicit triggering condition. It does not name an alternative sibling or state when not to use it, so routing between this and search_conferences is left partly to inference.

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