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

No annotations provided, so description carries burden. Discloses it builds an unsigned transaction (no on-chain effect) and that new authority is pinned for verification. But doesn't mention authorization requirements (must be current authority) or that it's a Solana transaction structure.

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?

Two concise sentences, front-loaded with purpose. No wasted words. Each sentence adds necessary information.

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 5 required params, no output schema, and medium complexity, the description covers core purpose but misses details like return format (unsigned transaction), what 'pinned' means, or that this is a Solana-specific tool. Adequate but not comprehensive.

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. Description adds context that changeMint/changeFreeze booleans control which authority transfers, but otherwise doesn't significantly augment schema descriptions. Marginal added value.

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 it builds an unsigned change-authority transaction for transferring mint/freeze authority. Verb 'build', resource 'unsigned change-authority tx', and purpose are specific. Distinguished from siblings like solknife_change_authority_execute (execute) and solknife_change_authority_read (read).

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?

Implies usage for changing authorities but lacks explicit when-to-use vs alternatives like revoke_authority_build. No prerequisites or context about when this tool is appropriate versus others. Minimal guidance.

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