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

With no annotations provided, the description carries full burden. It correctly frames the tool as a safe read operation ('Read') without side effects. It does not disclose error behavior (e.g., invalid mint) but the core behavioral trait is clear. No contradiction with annotations.

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 that conveys the entire purpose without redundancy. It is front-loaded with the verb and resource, making it efficient and easy to parse. Every word is necessary.

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?

The tool is simple (read two values) and the description adequately covers what it does. No output schema is provided, but the description implies the output (authorities and ownership status). Minor gaps exist (e.g., error handling, return format), but these are acceptable for a low-complexity read tool.

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% with descriptions for both parameters. The description adds meaning by linking 'mint' to 'current mint + freeze authorities' and 'owner' to 'whether owner holds either', explaining how the parameters are used in context, which goes beyond the schema's generic 'Solana address' 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 uses the specific verb 'Read' and clearly identifies the resource: 'a mint's current mint + freeze authorities and whether `owner` holds either'. It distinguishes from sibling tools like solknife_revoke_authority_build and solknife_revoke_authority_execute, which perform revocation actions, making its purpose unique and well-defined.

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 does not explicitly state when to use this tool versus alternatives. However, the purpose implies it should be used before performing a revocation to inspect current authorities. No explicit exclusions or alternative recommendations are provided, so guidance is only implied.

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