TRON infrastructure for AI agents.

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: session-scoped storage ('for this session') and side effects ('Unlocks all authenticated tools'). Missing details on whether this overwrites existing keys or security/storage guarantees.

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 sentences with zero waste: action (sentence 1), effect (sentence 2), prerequisite (sentence 3). Front-loaded with purpose. No redundancy with structured fields.

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?

Appropriate for an authentication setup tool with many dependent siblings. Explains unlocking capability sufficiently. No output schema present but unnecessary for a setter; however, lacks mention of validation errors or overwrite behavior.

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 has 100% coverage ('Your Merx API key (starts with sk_live_)'). Description adds prerequisite context ('if you already have an API key') but doesn't add format guidance beyond schema's sk_live_ prefix. Baseline 3 appropriate when schema does heavy lifting.

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?

Excellent specificity with 'Set your Merx API key' (verb + resource) plus session scope 'for this session'. Clearly distinguishes from sibling 'set_private_key' by specifying 'Merx API key' and listing unlocked categories (trading, balance, orders).

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?

Provides explicit prerequisite 'Use this if you already have an API key' implying when to use. Lacks explicit contrast with sibling 'set_private_key' (wallet key vs API key) which would prevent confusion given both set credentials.

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