TRON infrastructure for AI agents.

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

With no annotations provided, the description carries the full disclosure burden. It successfully notes authentication requirements but fails to indicate read-only safety, return value structure, pagination behavior, or what constitutes a 'monitor' in this domain (e.g., price monitors, transaction monitors).

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?

Extremely concise at two sentences. Information is front-loaded with the core action first, followed by the auth constraint. No redundant or wasted language.

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?

Despite low parameter complexity, the absence of both annotations and an output schema creates significant gaps. The description fails to explain what data structure is returned, what 'monitors' represent in this TRON/crypto toolset context, or behavioral constraints beyond authentication.

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 the baseline is 3. The description confirms the status filter is 'optional' (aligning with zero required parameters) but adds no semantic detail about the enum values (ACTIVE/CANCELLED) or query syntax beyond what the schema already provides.

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?

Clear verb (List) and resource (monitors) with explicit mention of the optional status filter. Distinguishes from sibling 'create_monitor' through the action verb, though it could explicitly reference the creation tool to strengthen differentiation.

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?

States 'Auth required' which is a necessary constraint, but provides no guidance on when to use this versus alternatives (e.g., when to filter by ACTIVE vs CANCELLED) or its relationship to 'create_monitor'. Lacks explicit prerequisites beyond authentication.

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