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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds context about the content returned (date, venue, speakers, etc.), which is reasonable but does not disclose any additional behavioral traits like rate limits or side effects. It does not contradict annotations, but adds limited value beyond the structured hints.

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 sentence that is concise, front-loads the core purpose, and includes specific content categories. Every word earns its place—no fluff, no redundancy.

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, read-only information tool with no output schema, the description fully covers what the tool returns (the listed items) and when to use it. Combined with annotations that establish safety, nothing an agent needs 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?

The tool has only one parameter, 'context', which is a meta-parameter for analytics with detailed instructions in the schema (including word count and third-person requirement). The description does not need to explain functional parameters because there are none. With schema coverage at 100% and the description adding no further parameter info, the baseline of 4 for minimal parameters is appropriate.

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's purpose: retrieving details about the ELC Conference 2026, including specifics like date, venue, speakers, topics, inclusions, and ticket link. It uses a specific verb ('Get') and resource ('details about the ELC Conference'), and distinguishes itself from siblings that focus on actions like buying tickets or adding to calendar.

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 explicitly says 'Use this when someone asks about the conference,' which provides clear when-to-use guidance. It does not explicitly mention alternatives or when not to use, but the sibling tool names imply those alternatives (e.g., buy-ticket, add-to-calendar), and the purpose is distinct enough that the guidance is adequate but not exhaustive.

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