get_token

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

No annotations exist, so the description carries the full burden. It implies a read but never says so, and it omits failure behavior for a bad/nonexistent token, whether data is on-chain vs cached, and what 'v2' gating means for callers expecting team/milestone fields.

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?

One short sentence with no filler. The parenthetical '(v2)' is slightly cryptic but doesn't bloat the 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?

No output schema and no annotations, so the description should sketch the return shape; 'curve state' plus team/milestones is a start but leaves the fields opaque. Adequate to identify the tool, not adequate to call it confidently.

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 0% and the single parameter 'token' is undocumented. The description says 'one AgentPad token' but never clarifies whether the value is an address, symbol, or numeric id — the one detail an agent most needs before calling.

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?

Names the specific resource ('Curve state of one AgentPad token') and the extra data returned (team, roadmap milestones), which distinguishes it from list_tokens and get_roadmap. No explicit verb, but 'state of one token' is unambiguous enough to act on.

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?

No statement of when to call this versus list_tokens or get_roadmap, no prerequisites, no note about what happens for an unknown token. The agent must infer that this is the single-token lookup.

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