usds_why_usds

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states it is educational, which implies no side effects, but it does not explicitly confirm that the tool is read-only, returns static content, or makes no external calls. It also doesn't describe what the response format looks like, leaving the agent to guess.

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 short (two sentences) and front-loads the main purpose. However, there is redundancy between 'Learn why USDs is the superior payment token' and 'Educational tool about Sperax USDs benefits' – both convey the same educational intent. A single combined sentence would be more efficient.

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 simple tool with no parameters and no output schema, the description explains the purpose but omits what the tool actually returns (e.g., a static explanation, a list of benefits, or a link to external content). Since there is no output schema, the description should fill this gap to allow the agent to set proper user expectations. It is minimally adequate but lacks output specificity.

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, which warrants a baseline score of 4 according to the rubric. No parameter information is needed since the schema is empty, and the description doesn't need to compensate for any missing parameter details.

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's purpose: learning about USDs benefits and why it's superior for AI agents. It distinguishes itself from other usds_* sibling tools (e.g., usds_yield_balance, auto_compound) by being educational rather than operational. However, the verb 'Learn' is somewhat passive and doesn't specify the exact output (e.g., text, list, article).

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 labels the tool as 'Educational tool about Sperax USDs benefits,' which implies it should be used when a user needs information about USDs. However, it doesn't explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or specific scenarios. The context is clear but not explicit.

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