build_cronset_unsigned

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

Discloses key behaviors: the tool never signs, defaults to testnet, returns unsigned JSON + preflight. It explains parameter ranges (repeatCount 0–256) and the meaning of startTime/startInSeconds. Given no annotations, this provides adequate transparency, though error handling is not covered.

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?

Concise at 4 sentences, front-loads the main purpose, and every sentence adds value. No redundancy or unnecessary details.

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?

Covers the main aspects: purpose, key parameters, return type, default network, and prerequisite. However, the return description ('unsigned JSON + preflight') is slightly vague, and more detail on output structure would improve completeness for a tool with no output schema.

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?

Adds significant meaning beyond the input schema: explains startTime as Ripple-epoch seconds, startInSeconds as convenience for now+N, and clarifies that omit repeatCount for one-off. Compensates for schema parameters (like delaySeconds) that lack descriptions.

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's purpose: 'Assemble an UNSIGNED CronSet — schedule a Hook's future self-invocations.' It uses a specific verb ('assemble') and resource ('CronSet'), and distinguishes from sibling tools like build_sethook_unsigned by focusing on cron scheduling.

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?

Provides clear context for use, such as the prerequisite ('account must have a Hook installed') and the cancel functionality ('set cancel:true for tfCronUnset'). However, it does not explicitly contrast with alternatives or specify when not to use it.

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