clip_flags

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

No annotations are provided, so the description carries the full burden for behavioral transparency. It reveals that the tool can read, add, or clear flags, and that clearing with 'All' removes all flags. However, it does not disclose what reading returns, whether operations are reversible, required permissions, or behavior when both add and clear are specified. Essential behavioral details are missing.

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?

The description is extremely concise: one sentence stating the actions and a short instruction. Every word is necessary and adds value. This is an example of efficient communication.

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?

Given the tool has three parameters (handle, add, clear) and no output schema, the description is insufficiently complete. It explains the three actions and a special clear value, but fails to describe return values for reading, valid flag names, default behavior, or multi-parameter interactions. This leaves significant gaps for an agent to use the tool correctly.

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?

The schema has no property descriptions (0% coverage), so the description must compensate. It adds meaning for the 'clear' parameter by specifying the special value 'All' to remove every flag. However, it does not explain the 'add' parameter or what valid flag values are, nor does it clarify whether 'read' is achieved by omitting both add and clear. Partial but not comprehensive.

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: 'Read, add or clear clip flags.' This specifies the verb and resource (clip flags) and distinguishes it from sibling tools like clip_markers which handle markers. However, it lacks clarity on how to execute the 'read' operation since the input schema has no parameter for reading; presumably reading occurs by default when no add/clear is provided, but this is not explicit.

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?

The description includes one usage instruction: 'Pass clear='All' to remove every flag.' This provides a specific case, but there is no guidance on when to use this tool versus alternatives like clip_markers or clip_find. There is no comparative context or explicit when-to-use/when-not-to-use advice.

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