get_ftso_feed

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

Given no annotations, the description partially bears the transparency burden. It reveals the return type (latest value, decimals, timestamp) and input flexibility (name or raw id), but lacks information on authorization, rate limits, error handling, or 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?

Single sentence that immediately conveys the core purpose and key details. No extraneous words, front-loaded with the primary action and resource.

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?

The description covers the essential inputs and output shape, but for a tool with no output schema and no annotations, it omits important context such as response structure details (e.g., exact keys), error conditions, and case sensitivity of feed names. It is adequate for simple use but leaves gaps for robust agent interaction.

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%, so the description must compensate. It adds that feed_id can be a feed name (e.g., 'FLR/USD') or a bytes21 id, which is meaningful beyond the schema's type-only definition. Network is not elaborated beyond the schema's enum, but overall the description adds significant parameter context.

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 retrieves the latest FTSO price feed, specifying the returned fields (value, decimals, timestamp) and the two identification methods (name or bytes21 id). This distinctly separates it from siblings like get_ftso_feeds_all or get_ftso_history.

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 when a single feed's latest data is needed, but does not explicitly state when to use this tool versus alternatives, or when not to use it.

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