TRON infrastructure for AI agents.

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

No annotations are provided, so the description carries the full disclosure burden. It successfully indicates persistence (distinguishing from ephemeral operations) and authentication requirements, but omits lifecycle details (how to delete/disable), trigger behavior specifics, or reversibility notes.

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 efficient two-sentence structure. Every element is high-signal: the verb+resource, the parenthetical type enumeration, and the auth prerequisite. No redundant or filler 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 moderate complexity (4 params, nested objects) and lack of annotations/output schema, the description covers the core creation purpose but has gaps around expected return values (e.g., monitor ID), error conditions, and lifecycle management (how monitors are stopped or expire).

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?

With 100% schema coverage, the baseline is 3. The description adds value by translating the enum values of monitor_type (delegation_expiry, balance_threshold, price_alert) into readable business terms (delegation expiry, balance, price alert) and implying the alert nature of the tool.

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 verb (Create) and resource (persistent monitor), and specifically enumerates the three supported monitor types (delegation expiry, balance, price alert) in parentheses, which distinguishes this from generic monitoring or analysis tools in the sibling list like analyze_prices or get_price_history.

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?

It provides a critical prerequisite ('Auth required'), but lacks explicit guidance on when to choose this over one-time checks (like get_balance) or how it relates to sibling list_monitors. The listing of monitor types offers implied usage context for selection.

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