wetrack_reorder_widgets

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

No annotations, so description carries the burden. It explicitly states that ALL widget IDs must be provided, not just the moved one, and that it persists for the current user. This goes beyond the schema and prevents a common mistake. It doesn't mention return values or error behavior, but that's less critical for a reorder operation.

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 sections: a purpose sentence and an Args block with explanation and example. No redundancy, front-loaded with the main purpose, and every sentence earns its place.

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?

For a simple reorder operation with one parameter, the description covers purpose, parameter semantics, and prerequisite. Could mention return value or idempotency, but it's not essential for an agent to call it correctly. Adequate for the tool's complexity.

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 no description for ordered_ids, but the description explains it fully: ALL widget IDs in desired order, not just the moved one, and provides an example. Also instructs to fetch current IDs first, adding significant meaning beyond the raw array type.

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 (persist) and resource (display order of current user's report widgets). Clear and distinct from sibling tools like wetrack_list_widgets or wetrack_update_widget, as it's the only reorder operation.

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 a clear prerequisite: get current IDs from wetrack_list_widgets first. Implies usage context (when reordering) but doesn't explicitly mention alternatives or when not to use. Since no other reorder tool exists, this is sufficient guidance.

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