get_susdd_supply

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

With no annotations provided, the description carries the disclosure burden. It explains that the output is a chain-level breakdown of sUSDD total supply, which is the core behavior. It doesn't mention return format or potential caveats, but for a zero-parameter getter this is sufficient and adds the chain dimension beyond the tool name.

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 two sentences, both useful. The first states the core function; the second provides a use case (Earn participation analytics). No wasted words, and the key information is front-loaded.

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?

For a zero-parameter read tool with no output schema, the description adequately explains what it does and when to use it. It could mention response format, but the chain breakdown is self-explanatory. The description is complete enough for an agent to select and invoke it.

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?

The tool has zero parameters, so the baseline score is 4. The description adds no parameter details because none are needed; the schema already covers 100% of parameters (none).

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 returns sUSDD total supply broken down by chain, which is a specific resource and scope. This distinguishes it from siblings like get_usdd_supply (likely USDD) and get_total_supply (generic) by narrowing to sUSDD and adding the chain breakdown.

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 explicitly says to use this tool for analytics on Earn participation per chain, providing a concrete use case. It does not name alternatives or state when not to use it, but the context is clear enough to guide selection among siblings.

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