ripple_time

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

With no annotations, description carries full burden. Only states 'Offline' and conversion types. No mention of error handling, multi-input behavior, or whether it returns one or all conversions. Lacks behavioral details.

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?

Two succinct sentences, no extraneous information. Front-loaded with the verb and resources. Excellent conciseness.

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?

Simple conversion tool with 3 optional params and no output schema. Description covers purpose and offline nature. Could briefly mention output behavior (returns all conversions), but overall reasonably complete.

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 0%. Description names the three time types but does not clarify how to use the parameters: e.g., provide one to get the others, or any combination. Ambiguity about input-output relationship reduces value.

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?

Clearly states the tool converts between three specific time formats (Ripple, Unix, ISO 8601), including the definition of Ripple time. Differentiates itself from sibling tools which are primarily account/transaction retrieval.

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?

Mentions 'Offline' indicating no network dependency, and context that Xahau uses Ripple time. Does not explicitly state when to use vs alternatives, but the conversion purpose is clear and distinct from siblings.

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