hedera_delete_schedule

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

No annotations provided. Description discloses that the tool builds an unsigned deletion (i.e., produces a transaction, not directly deleting) and requires admin key. Adds behavioral context but lacks details on side effects or limits.

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?

Single sentence, no fluff. Could be improved by front-loading the essential info (e.g., deletion of schedule, unsigned) but still concise.

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?

No output schema or annotations. Description does not explain what the tool returns (e.g., unsigned transaction bytes) or how to proceed after building. Incomplete for reliable agent invocation.

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 has 0% description coverage, and description provides no explanation for parameters scheduleId or payerAccountId. Agent cannot infer their purpose or format from description.

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?

Description specifies action (build deletion) and resource (scheduled transaction), distinct from sibling tools like create or sign. However, 'Build (unsigned)' may imply it only prepares a transaction, not executes deletion, which could cause ambiguity.

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?

States 'requires admin key' as a precondition. No explicit when-to-use or alternatives, but among siblings, only this tool deletes schedules, so context is implied.

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