keyInfo

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

States read-only and that the call is rejected without a valid key. No annotations are provided, so the description carries full burden. It could mention potential error codes or return structure, but current details are sufficient for basic understanding.

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?

Three sentences, each serving a distinct purpose: describing what it does, when to use it, and prerequisites. No redundant or vague language.

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 no output schema, the description effectively outlines return values (plan, quota, requests remaining, expiry) and prerequisite (configured key). For a simple informational tool, this is complete and leaves no critical gaps.

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 zero parameters, and the description confirms 'takes no parameters'. Schema coverage is 100%, and the description adds no unnecessary param info beyond stating the absence.

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 gets details and usage for the current API key, listing specific fields: plan, quota, requests remaining, expiry. It distinguishes itself from sibling tools (e.g., getCoins, getTickers) by focusing on key info rather than market data.

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?

Explicitly provides usage context: 'Use for 'what plan am I on', 'how many requests are left', 'is my API key valid''. Also notes read-only nature and prerequisite of a configured COINPAPRIKA_API_KEY, guiding appropriate invocation.

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