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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered; the description still adds real behavior beyond them — the capped five-summary search result, the fact that summaries carry no schemas, and the guarantee 'Discovery never executes an operation.' It stops short of describing output shape or behavior on an unmatched name, but with an output schema present that is not required.

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 purpose, then the lookup workflow, then the no-execution guarantee. No filler or restatement of the name.

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 two-parameter discovery tool with full schema coverage, annotations, and an output schema, the description supplies everything an agent needs: purpose, the two-phase usage pattern, and the safety guarantee. Nothing critical 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 description coverage is 100%, so the per-parameter ground is covered (topic list for query, 'exact name from search' for operation). The description adds sequencing semantics the schema cannot express: query is the entry point, operation is the second-phase lookup keyed to a search result. Useful, though it does not add syntax or format detail beyond that.

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 ('Discover advanced Uxia operations') and immediately defines scope: it is a discovery tool, not an executor. An agent can distinguish it from read_advanced or edit_draft_advanced without opening any 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?

Gives an explicit two-step workflow (search to get up to five summaries, then supply an exact operation name to fetch the schema) and names the downstream tools (read_advanced, edit_draft_advanced) that require that schema. The condition selecting each parameter mode is spelled out rather than inferred.

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