notary_stats

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

Discloses that the tool is free and returns aggregated live data with no authentication required. No annotations exist, but description compensates by clarifying no side effects or authorization needs. Lack of rate limit info is minor for simple stat 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?

Single sentence with all key information front-loaded ('FREE — live aggregate stats'). No superfluous words; every phrase adds value.

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 simple stat tool with no parameters, the description fully covers what it does and what it returns. No output schema is needed as the description lists the specific stats. Sibling tools are clearly different.

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 100%). Description adds value by detailing the returned metrics (total notarizations, 24h volume, top models, Merkle batches), which is not inferable from the empty schema.

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 'live aggregate stats' and enumerates specific metrics (total notarizations, 24h volume, top models, Merkle batches). Distinguishes from siblings like notarize_batch (action) and get_receipt (individual record).

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?

Highlights 'FREE' and 'No wallet needed', implying unrestricted use for quick overview. Provides clear context but does not explicitly contrast with alternatives; however, siblings are functionally distinct, so guidance is adequate.

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