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

The annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, indicating no destructive side effects. The description adds value by revealing the approximate token size (a few thousand tokens) and the internal structure (grouped by category, one-line titles). It does not contradict annotations, so no flag. Slight deduction because the description could mention that no parameters are needed, but it's already implied.

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?

The description is slightly verbose but every sentence adds value: it states the content, token budget, comparison to search_engines, and post-call workflow. The information is front-loaded. It could be slightly more concise, but the detail is justified.

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?

Given the tool has zero parameters, full schema coverage, and rich annotations (readOnly, openWorld, idempotent), the description provides all necessary context: what the catalog contains, how large it is, when to use it, and how to chain it with sibling tools. No output schema exists, but the description explains what it returns.

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?

There are zero parameters, and the schema coverage is 100% (empty object). The description does not need to elaborate on parameters, and it correctly focuses on the output and usage. This is a perfect handling of a parameterless tool.

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 clearly states it returns the FULL ReefAPI catalog with every engine's one-line title grouped by category. It explicitly distinguishes from the sibling search_engines by emphasizing comprehensiveness: 'SCAN IT AND PICK THE BEST ENGINE YOURSELF.' The verb 'get' is straightforward, and the resource 'catalog' is well-defined.

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?

The description provides explicit usage guidance: 'Use this whenever search_engines didn't surface the right engine (or to be sure you didn't miss a better one).' It also specifies the ideal workflow after using this tool: 'get_engine_schema(engine) -> get_action_schema -> call_engine.' This effectively tells the agent when to use this tool vs alternatives and what to do next.

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