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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that operationId yields the full path/query/body contract, but says nothing about pagination behavior (limit/offset with a hard cap of 50) or the shape of list results, which matters for an open-world discovery tool.

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, each doing distinct work: what it returns, how to query it, when to call it and where to go instead. No repetition of the title or schema.

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 read-only discovery tool with no output schema, the description covers purpose, query modes, escalation path and the fallback rule. The one gap is pagination: with limit capped at 50 and offset available, an agent is not told that results may be truncated or how to page through them.

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 only 25% — only 'search' is documented in the schema. The description compensates by explaining both ambiguous parameters: search takes plain words, and operationId returns that operation's full path/query/body contract. limit and offset remain undescribed, though they are conventional pagination names.

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 all current Management API operations') and narrows the scope by noting it covers settings and modules absent from the dedicated tools. The mention of plain-word search and operationId lookups makes the two modes of use unambiguous.

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?

'Call this before saying an action is unsupported' gives an explicit trigger condition, and the final sentence routes protected actions away to list_commands. That is a named alternative with the condition that selects it, not implied usage.

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