barker_market_trend

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

With no annotations provided, the description must disclose all behavioral traits. It states the lookback range and that it returns a historical trend, which is adequate. However, it does not mention read-only nature, potential rate limits, or output format details, leaving gaps for an agent.

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 concise with one sentence and example phrases. It efficiently conveys purpose and usage without extraneous text. Front-loading the main description and then examples works well.

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 (1 parameter, no output schema), the description covers purpose, parameter, and usage context. However, it omits what the output looks like (e.g., a time series, delta values), which is needed for an agent to process the result 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 coverage is 100% (parameter 'days' with min/max and description). The description adds '7–180 days' which matches the schema. No additional meaning beyond the schema is provided, so a score of 3 is appropriate.

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 'Historical APY trend for stablecoins vs. US Treasury benchmark over a lookback window', which differentiates it from sibling tools like barker_defi_vaults and barker_market_overview. However, it uses a noun phrase rather than an active verb, slightly reducing clarity.

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 explicit usage examples ('DeFi vs treasury', 'is stablecoin APY going up') that help an agent understand when to invoke this tool. It does not mention when not to use it or list alternatives, which would have improved the score.

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