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

Annotations declare readOnlyHint=true and destructiveHint=false, which the description does not contradict. It adds context about availability (public MCP vs x402 micropayments), pricing tiers, and free access, which is useful behavioral context beyond the annotations.

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 dense but every sentence serves a purpose: it states the primary function, lists access methods and pricing, clarifies what requires auth, and gives a call-to-action. It's front-loaded with 'START HERE' and uses concise phrasing without fluff.

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 parameterless catalog tool with read-only annotations, the description covers all necessary information: what it returns, how to access it, pricing, and when to use it. No output schema exists, but the description adequately describes the return as a tool catalog. 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?

The tool has zero parameters, and schema coverage is 100% (vacuously). The description does not need to explain parameters; the baseline for 0 params is 4, and no additional semantics are required.

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, explicitly naming it as the entry point to discover tools by role or vertical. It distinguishes itself from the many sibling tools by being the catalog overview, not a specific data getter.

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 opens with 'START HERE' and instructs to call this first to discover tools by role or vertical, providing clear when-to-use guidance. It also notes that some features (org intelligence, agent governance, role briefs) require OAuth, implicitly telling agents when auth is needed.

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