account_verify_signature

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

With no annotations provided, the description carries full burden but reveals little about behavior. It states the cryptographic verification purpose but doesn't disclose what happens on success/failure (e.g., returns boolean, throws error), whether it's read-only (implied but not explicit), network effects, rate limits, or authentication requirements. For a cryptographic verification tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and uses precise technical language ('cryptographically verify', 'NEAR account's public key'). Every word earns its place.

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 cryptographic complexity, no annotations, and no output schema, the description is incomplete. It doesn't explain what verification entails (e.g., public key lookup, hash comparison), return values (success/failure indicators), error conditions, or network implications (mainnet vs testnet). For a security-critical tool, this leaves significant gaps.

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 description coverage is 75% (good), so baseline is 3. The description adds minimal value beyond the schema: it mentions 'NEAR account' (implied by accountId parameter) and 'signed piece of data' (implied by data and signatureArgs). It doesn't explain parameter relationships (e.g., data must match what was signed) or provide examples, so it meets but doesn't exceed the baseline.

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 clearly states the specific action ('cryptographically verify') applied to a specific resource ('a signed piece of data') with a specific target ('against a NEAR account's public key'). It distinguishes from siblings like account_sign_data (which creates signatures) and account_view_account_summary (which doesn't verify cryptographic proofs).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a signature from account_sign_data first), when verification is needed (e.g., authentication, transaction validation), or what to do if verification fails. Siblings like account_sign_data are clearly related but no comparison is made.

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