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

No annotations present. The description does not disclose behavioral traits such as authorization needs, irreversible effects, or failure behavior beyond listing possible outcomes. Agent must infer safety profile.

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 with no filler. Every word adds value, clearly stating action and return type.

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 simple schema (two parameters) and no output schema, the description provides basic return type info but lacks guidance on prerequisites (e.g., must have called /build). 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 description coverage is 100%, so baseline is 3. The tool description adds no parameter semantics beyond what the schema already provides, but the schema descriptions are detailed.

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 it submits a wallet-signed swap transaction, with specific verb and resource. The name 'solknife_swap_execute' and sibling 'solknife_swap_order' provide differentiation within the suite.

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 explicit guidance on when to use this tool versus alternatives like 'solknife_swap_order' or other execute tools. Usage is only implied by the name and sibling context.

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