notary_pubkey

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

No annotations provided. The description conveys it is a free, read-only operation returning a known key, but does not detail side effects, idempotency, or access requirements beyond 'no wallet needed'.

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, fully front-loaded with 'FREE', no filler, every word 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?

No output schema or annotations, but for a simple key retrieval tool with no parameters, the description adequately covers format, purpose, and constraints for offline use.

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, and schema coverage is 100%. With zero parameters, the baseline is 4, and the description adds no additional semantic value beyond what the schema indicates.

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 explicitly states it provides the notary's Ed25519 public key for offline signature verification, specifying format (base64, raw 32 bytes) and distinguishing it from siblings like verify_attestation.

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?

Clearly states 'No wallet needed' and implies usage for offline verification, but does not explicitly mention when to avoid using it compared to other notary tools.

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