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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the burden is lowered. The description adds useful domain context (catalog is FREE, fixed ID range, explicit return fields including catalog_url) beyond structured fields. It stops short of stating whether the catalog is static or fetched live, but adds genuine value.

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?

Two sentences, tightly front-loaded with the resource and ID scope, then the returned fields, then the operational next step. No filler.

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 zero-param catalog with no output schema, the description enumerates the returned fields and the follow-up action, which is exactly what an agent needs. Nothing material 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?

Zero parameters, so baseline is 4. The description correctly documents that no input is needed and instead describes the output surface, which is the most useful information for a 0-param 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?

States a specific verb+resource ('catalog of Rainmaker wells'), enumerates the exact ID set covered (001–012, 015, 016), and lists the returned fields. This distinguishes it from siblings catalog-url (URL only) and recommend-well (recommendation logic) without opening either schema.

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?

Provides a clear post-condition workflow: 'After picking a well, open {origin}/mcp directly.' However, it does not explain when to use list-wells vs. recommend-well, which is the key sibling choice for an agent with a vague intent.

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