notarize_inference

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

Discloses that only hash is retained, not prompt/response, and mentions cost and required keys. Missing details on idempotency or error scenarios, but overall transparent.

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?

Three sentences, no fluff. First sentence clearly states purpose, second details output, third provides key behavioral info. Front-loaded efficiently.

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 tool with no output schema, description adequately explains return value and notable behaviors. Could mention potential errors or atomicity, but still quite complete.

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?

Schema covers all parameters with 100% description. Description adds context about receipt contents (sha256, Ed25519) but does not significantly enhance parameter semantics beyond 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?

Description clearly states 'Get a cryptographic receipt for one AI inference' with specific verb and resource. Differentiates from siblings like 'notarize_batch' by focusing on single inference.

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?

Cost and required wallet keys are mentioned, but no explicit when-to-use vs alternatives or exclusions. Sibling tools provide context, but description itself lacks direct guidance.

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