get_discovery_metadata

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

Discloses it's a fetch operation and lists sources. 'Free' hints at no cost/rate limit. With no annotations, this provides adequate transparency for a no-parameter tool.

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?

One concise sentence with no waste. Information is front-loaded and every word is informative.

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 zero parameters, no output schema, and no annotations, the description fully covers the tool's purpose and behavior. No additional context needed.

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?

No parameters exist; schema coverage is 100%. The description adds value by specifying what is fetched beyond the empty schema, meeting the baseline and exceeding it.

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?

Clearly states the tool fetches public discovery metadata from specific files (index.json, llms.txt, openapi.json, x402 well-known metadata). Distinguishes from sibling tools which focus on analysis and risk.

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?

Implies usage when public discovery metadata is needed. The 'Free' note adds context. No explicit when-not or alternatives, but siblings are sufficiently different so no confusion.

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