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

Annotations only say readOnlyHint=false and destructiveHint=false. The description adds genuinely useful behavioral context: the output is soulbound, on-chain, and immutable, which tells the agent the credential cannot be transferred or undone. It stops short of disclosing cost/gas requirements or authorization needs.

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 tight sentences; the core action and artifact are front-loaded, and each subsequent sentence adds a distinct fact (on-chain proof, onboarding position). No filler.

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 write tool with no output schema and thin annotations, the description covers the artifact, its immutability, and its onboarding position. It omits what the call returns (e.g., certificate address) and any cost or prerequisite detail, a modest but real gap.

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 100%, so all four parameters (kernelDid, capabilityType, assuranceTier, metadata) are already documented, including the nested metadata object. The description adds no syntax, format, or constraint detail beyond the schema, so baseline 3 applies.

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 gives a specific verb (mint) and a precise resource (soulbound capability certificate, cNFT via Metaplex Core) plus the target object (a kernel). It is clear what the tool produces, though it never distinguishes itself from close siblings like create_capability or register_capability_ip.

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?

"Step 5 of onboarding" implies sequencing context and thus a rough when-to-use signal, but there is no explicit precondition list, no statement of when NOT to use it, and no routing to sibling alternatives such as create_capability.

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