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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds genuinely useful behavior beyond them: the returned menu maps questions to tool names, and it implies no state mutation. It does not, however, describe pagination or the shape of the returned list in detail.

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?

One compact, front-loaded sentence that leads with the trigger conditions and ends with the return value. It is dense but every clause earns its place; there is no filler or repetition of the title.

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 carries the return-value burden and does so adequately by explaining that the response is a menu of real questions mapped to tool names. An agent has everything needed to call it correctly, though the exact response format is only described in prose.

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 100% and the single optional 'context' parameter is fully documented in the schema itself, including that it is recorded as intent and never changes the answer. The description adds nothing about the parameter, so the baseline 3 applies.

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 precise verb+resource: it handles greetings, liveness checks, and generic messages, and returns a menu of questions mapped to tools. It explicitly positions itself as the fallback relative to the specific sibling tools, so an agent can distinguish it from buy-ticket or get-conference-info without opening a schema.

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?

It names explicit trigger cases ('hi, hello', connectivity/liveness test, 'what can you do', any message too general to match a specific tool below) and explains what to do with the result ('the next call can go straight to the right tool'). When-to-use and the routing outcome are both stated.

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