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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is covered. The description adds value by specifying 'public', implying no authentication is needed, and by outlining the explanatory content, which helps set agent expectations about the response topic.

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 compact, with a front-loaded statement of the tool's nature and scope followed by direct usage guidance. Both sentences earn their place, and there is no redundant repetition of the title or annotations.

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 zero-parameter schema, the read-only/idempotent annotations, and the simple descriptive nature of the tool, the description covers what the tool does, what content it provides, and when to invoke it. No critical behavioral or usage information is missing for an AI agent to select and call it correctly.

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 the schema description coverage is 100%, so there is no parameter ambiguity. The description appropriately avoids inventing parameter details and instead focuses on the tool's purpose, matching the baseline expected for a parameterless 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?

The description uses a specific verb ('explain') and a clear resource ('Noemic'), and enumerates the exact topics covered: the open direct wagering network, source provenance, human approval, and no-custody boundaries. It also distinguishes itself from sibling tools by explicitly labeling this a public, read-only explanation rather than an actionable betting or authentication operation.

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 clearly states when to use the tool: 'Use when a person asks what Noemic is, why it can be trusted, or how matching works.' It does not explicitly name alternatives or describe when not to use it, but the use cases are concrete and differentiate it well from the sibling action-oriented tools.

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