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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety and side effects. The description adds the aggregation behavior and normalization aspect, but does not disclose additional traits like rate limits or authentication requirements. With annotations present, the description adds moderate context.

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 a single sentence that conveys the core purpose concisely. It is front-loaded with the key action and resource, with no superfluous words.

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?

Given the tool's simplicity (3 optional params, safe, output schema present), the description covers the main functionality and aggregation behavior. It is nearly complete but could briefly clarify what 'normalized' means or hint at the output structure. Since an output schema exists, the omission is acceptable.

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%, putting full burden on the description. Only 'venue' is hinted at via 'venue=None aggregates', while 'market' and 'caller_id' have no explanation. This is insufficient for a tool with three optional parameters.

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 provides normalized funding/borrow rates across multiple venues, with the special behavior of venue=None aggregating data. This is specific and distinguishes it from siblings like perp_funding_rates, which likely targets a single venue.

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 implies usage contexts by mentioning venue=None aggregation, but it does not explicitly state when to use this tool versus alternatives like perp_funding_rates. No when-not-to-use or exclusion criteria are provided.

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