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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description earns extra credit by disclosing the return shape (nine independent actions with tool mappings) and that no business records are read or mutated, plus the interaction protocol of pausing for the user's selection.

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, front-loaded with the action and triggers, then scope, then the required follow-up behavior. No filler or restated field names.

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 job of saying what the agent receives — it does exactly that (nine actions, mapped tools, workflow guidance) and adds the interaction expectation. Nothing needed to call a zero-arg menu tool 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 takes zero parameters, so the schema baseline of 4 applies and there is nothing further for the description to disambiguate.

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 and resource — 'Show the Otis chat menu' — and pins the triggers (/otis, 'show Otis menu', getting started). It also declares what comes back (nine actions with mapped tools plus workflow guidance), which separates it from every sibling tool that actually touches records.

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?

Gives concrete invocation triggers and a clear scope boundary ('without reading or changing business records'), plus the follow-up instruction 'Wait for the user's choice.' It doesn't explicitly name a sibling as the alternative, but the entry-point framing makes the when-to-use obvious.

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