issue-attestation

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that this is a blockchain transaction requiring wallet authentication, gas costs, or that it creates an on-chain record. The high number of params (11) and required wallet fields suggest significant setup, which is not explained.

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 sentence of 15 words, front-loaded with the key purpose. Every word earns its place, making it highly concise and easy to parse.

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?

With 11 parameters, no output schema, and no mention of return values or side effects (e.g., transaction hash, attestation UID), the description leaves significant gaps. The complexity of issuing an on-chain attestation (requiring wallet setup, gas, etc.) is not addressed.

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 coverage is 100%, so baseline is 3. The description adds value by specifying that 'data' should use schema encoder format and that 'walletData' should contain saved wallet file content. This provides useful guidance beyond the bare schema descriptions.

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 action (issue), the resource (attestation), the network (Rootstock), and the service (RAS). This directly differentiates from sibling tools like verify-attestation, revoke-attestation, and list-attestations.

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?

No guidance on when to use this tool versus alternatives. Siblings include schema creation (create-schema) and other attestation operations, but the description does not specify prerequisites (e.g., needing a schema UID) or when to prefer this over others.

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