brc_delete_sales_entry

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

Discloses the two-step confirmation behavior and payload preview. Lacks details on consequences of deletion (e.g., irreversibility), but annotations are absent so description carries the burden.

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 sentences: first states purpose, second details process. No fluff, front-loaded, but could be slightly more structured for readability.

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?

Sufficiently covers the confirmation workflow for a delete tool with no output schema. Does not explain errors or prerequisites, but overall complete for agent usage.

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 value for confirmWrite parameter by explaining the preflight/confirmation workflow. Schema covers 75% of parameters; description compensates with usage details beyond 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 it deletes a BRC sales entry by ID using timestamp confirmation. It differentiates from sibling delete tools by specifying the unique two-step confirmation process.

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 explicit step-by-step usage: first call without confirmWrite, show draft, then retry with confirmation. However, it does not compare to alternatives like other delete tools.

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