spectra_get_ve_info

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

No annotations provided, but description discloses on-chain reading from Base chain, auto-population logic, and the boost formula. Lacks explicit mention of read-only nature and absence of side effects.

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?

Concise and well-structured: one-line summary, explanation of data source, formula, and usage note. Every sentence adds value.

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?

With no output schema, description compensates by stating output is an exact boost multiplier. Could elaborate on other return fields (e.g., total supply) but sufficient for agent decision-making.

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?

All 5 parameters have schema descriptions, but the description adds significant value by explaining the formula, auto-population when wallet_address is given, and the requirement of capital_usd with ve_spectra_balance.

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?

Description clearly states it gets live veSPECTRA info and computes boost scenarios using a specific formula. It distinguishes itself from sibling tools by focusing on governance token boost calculation.

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?

Clearly states usefulness for understanding veSPECTRA needed for max boost. Does not explicitly state when not to use, but context is clear among siblings.

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