coingecko_treasuries

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

No annotations are present, so the description carries full burden. It implies a read-only operation by referencing 'public crypto treasuries tables' but does not explicitly confirm non-destructive behavior, authentication needs, or rate limits. The mention of 'supports the documented vs_currency enum' adds some transparency, but key behavioral traits are omitted.

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 three sentences, front-loading the core purpose and adding a relevant detail about the vs_currency enum. It is efficient with no redundant information, though the second sentence could be merged with the first.

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?

With no output schema, the description should at least outline the structure of returned data. It mentions 'normalized entity rows' but does not clarify fields, columns, or pagination behavior. This lack of detail hampers an agent's ability to interpret results.

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% with each parameter having a clear description (e.g., 'Treasury asset filter, default all'). The description adds only that vs_currency is an enum, which is already in the schema. No additional meaning or usage nuance is provided beyond the 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 it returns normalized entity rows from CoinGecko's public crypto treasuries tables. It specifies the resource ('crypto treasuries') and a supported parameter (vs_currency enum), distinguishing it from sibling tools like coingecko_coin or coingecko_markets. However, it could more explicitly define what 'treasuries' entails.

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?

No guidance is provided on when to use this tool versus alternatives among the many sibling CoinGecko tools. The description does not mention context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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