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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context: the Build Envelope filtering (out-of-envelope options are never advertised) and the mode=overview behavior returning the app map. No contradiction.

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?

A single well-structured sentence with semicolon-separated details. The primary purpose is front-loaded, and every clause earns its place without 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 read-only catalog retrieval with 3 parameters, 2 enums, and no output schema, the description covers the views, the filter, and the mode behavior. Combined with annotations, nothing essential 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 coverage is 100% and all parameters have descriptions. The description restates the views, query, and mode but adds no new meaning beyond the schema (e.g., the 'app map' phrasing is already in the schema). Baseline of 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 specific verb+resource ('The organization's served catalog') and clearly distinguishes from siblings by enumerating the exact views (models, tools, agents, etc.). It also adds a scoping constraint (Build Envelope) that separates it from generic list tools.

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 tells you what it returns (views, query, mode) and implicitly covers when to use it (to browse the catalog). However, it does not explicitly contrast with alternatives like list_agents or get_agent, though the enumerated views make the boundary clear.

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