donate_triage

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

With no annotations, the description carries the full burden, and it does add the crucial disclosure that nothing is moved — important because "sort into a donate bag" reads as a mutation. It stops short of stating permissions, whether the result is persisted, or that the output is a proposal rather than an applied change.

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 short sentences, front-loaded with the operation and followed by the safety caveat. "Act only when you're ready" is mildly redundant filler, but there is no bloat overall.

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?

The output schema exists, so return values need not be described, and the non-destructive nature is covered. Yet for a triage tool with one undocumented threshold parameter, the description leaves unclear how the cutoff is applied and how the agent should proceed to actually donate.

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% and the single parameter min_days is never named or explained. "By last-worn date" hints that a wear-date threshold is involved but gives no units, no mention of the 180-day default, and no indication of what happens at the boundary.

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?

States a specific verb and resource: it sorts the closet into donate-bag versus keeper buckets keyed on last-worn date, which is distinct from list_items, unworn_report, and mark_donated. However, it never names or contrasts those siblings, so an agent must infer the division of labor from names alone.

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?

"Read the list first, act only when you're ready" implies a preview-then-commit workflow, which is real usage guidance. But it never says which tool performs the commit step (mark_donated) or when unworn_report would be the better choice, so the guidance is only implied.

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