midnight_transfer_tokens

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

With no annotations provided, the description carries full burden. It discloses transfer types, fees, and security via environment variable, which is good. However, it does not explain return values, error handling, or whether operations are reversible – leaving gaps in behavioral transparency.

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 very concise, using bullet points and sections to present transfer types, requirements, fees, and security. Every sentence adds value, and the structure is front-loaded with the main purpose. No unnecessary text.

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 parameters, no output schema, and no annotations, the description covers key aspects (purpose, types, fees, requirements) but lacks details on return value, error conditions, and specific usage of parameters like 'network' and 'shielded'. Some gaps remain, making it adequate but not fully complete.

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 80% (4 of 5 params have descriptions), so the schema already covers most parameters. The description does not add significant meaning beyond the schema; for example, the 'shielded' parameter is only mentioned in the description as a type but its allowed values are not clarified. The 'memo' parameter lacks description in both schema and tool description, so the description does not compensate.

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 tool transfers tDUST tokens, with specific verb 'Transfer' and resource 'tDUST tokens'. It distinguishes from sibling tools like midnight_get_balance by focusing on transfers and even detailing transfer types (Standard/Shielded), making its purpose unambiguous.

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 provides clear context for usage, including requirements (sufficient balance, network, gas) and fees. It does not explicitly state when not to use or offer alternatives, but the context implies appropriate scenarios. Sibling tools do not overlap in functionality, so exclusion is less critical.

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