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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral detail: results are capped at 10, each result includes id, title, and url, and a follow-up fetch is needed for full records. No contradiction with annotations exists.

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 cover purpose, output behavior, and follow-up action without filler. The description is front-loaded with the operation and scope, making it easy to scan.

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 tool with one required parameter and no output schema, the description covers query semantics, result limit, result fields, and the next step for full records. The main omission is guidance on empty results and explicit differentiation from the similarly named 'search_conferences' sibling.

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 describes 'query' only as 'What to look for,' which is generic. The tool description enriches this by enumerating valid query types: city, topic, company, or conference name. This gives the agent practical guidance on how to form a useful query.

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 states a specific verb and resource: 'Search conferences by free text', and details the output shape. It is clear, but it does not explicitly distinguish itself from the sibling tool 'search_conferences', which appears to 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?

The description clearly sets the context: use this tool for free-text conference searches by city, topic, company, or name. It also instructs the agent to pass an id to fetch full records, but it does not explicitly say when not to use this tool or how to choose between this and 'search_conferences'.

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