getCoinGreeks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds valuable behavioral context: a 10 req/s rate limit, aggregated-by-base-coin behavior, and the fact that Greek values are returned as string numbers. No contradiction with annotations.

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 compact and front-loaded, leading with the core function and return fields, then adding rate limit and parameter guidance. Every sentence adds useful information without repetition or filler.

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 read-only query with one optional parameter and no output schema, the description covers the return contents, filtering semantics, rate limit, and value formatting. An agent has everything needed to call it correctly.

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 description coverage is 0%, but the description fully compensates by explaining the baseCoin parameter: usage examples (BTC, ETH, SOL), optional behavior, and the result when omitted. This gives the agent complete parameter understanding despite the sparse schema.

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 a specific verb and resource: 'Query option Greeks aggregated by base coin' and names the returned fields (delta, gamma, vega, theta). It is unambiguous about what the tool does, though it does not explicitly differentiate itself from sibling tools like subscribeGreeks or getHistoricalVolatility.

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 'Agent hint' provides clear context: use for options risk management, pass baseCoin to filter, and omit to get all base coins. It does not mention alternatives or when not to use this tool, but the usage context is clear and actionable.

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