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

Annotations already declare read-only and non-destructive behavior. The description adds substantial context beyond that, including access methods (public MCP no auth, x402 micropayments on Base with exact pricing tiers, and OAuth for specific features). This discloses authentication requirements and cost implications, which are valuable behavioral traits.

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 immediately states the purpose. It then efficiently lists access methods and pricing in a structured format, followed by a direct call-to-action. Every sentence provides actionable information, with no wasted words.

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 zero-parameter, read-only catalog tool, the description fully covers purpose, access, pricing, and usage timing. Since there is no output schema, the description sufficiently implies the return value (a catalog) through its explicit statement. It is complete for the tool's intended use.

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 tool has zero parameters, so the schema is trivially covered. The description adds context about the tool's role as a discovery catalog, but no parameter-level detail is needed. Baseline 4 is appropriate per the rubric for 0-parameter tools.

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 the tool 'Returns the complete Stratalize tool catalog' with a specific verb and resource. It also distinguishes itself from sibling benchmark tools by serving as the entry-point discovery tool, making its purpose 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?

The description explicitly says 'START HERE' and 'Call this first to discover tools by role or vertical,' providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or name alternative tools for exclusions, so it falls short of a perfect 5.

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