d3p_rate-limit-calc

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

Without annotations, the description carries full burden. It discloses cost (3 sats), endpoint, and parameter details. It implies a read-only calculation, but does not detail side effects or output structure. Overall transparent given tool simplicity.

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 very concise: two sentences plus compact metadata. It front-loads the purpose and provides parameter details efficiently. No unnecessary content.

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?

For a simple calculator with an output schema, the description covers the essential inputs and purpose. It could mention that reset_time should be a future timestamp, but it is largely complete and sufficient for the tool's complexity.

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 schema only has a generic 'params' string with 0% coverage. The description compensates by specifying expected JSON fields (remaining, reset_time) and their types, adding crucial meaning 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 'Calculate wait time and strategy for rate-limited API calls', which is a specific verb and resource. It distinguishes itself from sibling tools which are unrelated (e.g., weather, shitpost, etc.).

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 implicitly tells when to use the tool: when needing to calculate wait time for rate-limited API calls. No exclusions are needed since siblings are not competitors, but explicit 'when to use' guidance is missing.

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