getFixedTermProduct

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

With no annotations, the description carries full burden. It discloses that no authentication is required and rate limit is 50 req/s. As a 'Query' tool, it implies read-only behavior, but does not explicitly state non-destructiveness. The provided info adds valuable behavioral context beyond a basic description.

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 extremely concise: two sentences and a rate limit note. It is front-loaded with the core purpose. No unnecessary 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 (one optional parameter, no output schema), the description covers the main operation but omits crucial parameter semantics. An agent would lack guidance on how to specify the coin. Without explaining the parameter, the description is incomplete for practical use.

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 input schema has a single parameter 'coin' with no description (0% coverage). The description fails to mention this parameter at all, leaving it unclear what values are valid or if it is required. Given the low coverage, the description should compensate by explaining the parameter's role, but it does not.

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 'Query fixed term product information' with concrete examples like tiered APY, min/max stake amount, product status. This specific verb+resource combination distinguishes it from sibling tools such as getFixedTermOrder or placeFixedTermOrder.

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 provides authentication and rate limit info, which is helpful for usage. However, it does not explicitly state when to use this tool over alternatives (e.g., getFixedTermPosition) or when not to use it. The usage context is implied but not formalized.

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