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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent. It adds valuable behavioral context by disclosing authentication requirements and the pricing structure for different service tiers, which goes beyond the annotation fields and helps set expectations for the agent.

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 front-loaded with 'START HERE' and the core purpose, followed by compact pricing and auth details. While it packs many specifics into three sentences, each piece (pricing tiers, OAuth requirement, domain coverage) serves a functional purpose for the agent deciding whether and how to invoke the tool.

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 no parameters, no output schema, and siblings are narrow query tools, the description is complete enough. It covers what the tool returns, the domains it spans, access methods, and cost implications. It could mention the response format, but the catalog nature is clear enough for an agent to proceed.

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 input schema has zero parameters, so the baseline of 4 applies. The description correctly avoids parameter details since none exist. It adds value by explaining the tool's role and output scope, which is sufficient given no params to document.

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 opens with 'START HERE' and clearly states the tool 'Returns the complete Stratalize tool catalog', a specific verb+resource. This distinguishes it from sibling tools like get_resolve_price_threshold and get_verify_crypto_price, which focus on specific price verification rather than a broad catalog discovery function.

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 explicitly says 'Call this first to discover tools by role or vertical', providing clear when-to-use guidance. It also outlines access modes (public MCP, x402 micropayments, OAuth) giving practical context, though it does not explicitly mention when not to use the tool or alternative entry points.

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