props_clear

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

No annotations are provided, so the description carries full burden. 'Clear' implies a destructive action, but it doesn't specify whether this is reversible, requires specific permissions, affects other props or displays, or what happens after clearing (e.g., does it return confirmation?). The description lacks details on behavioral traits like side effects or error conditions.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with one parameter, making it easy to parse and understand quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'clear' entails operationally, potential side effects, or return values. For a tool that likely performs a mutation (clearing a prop), more context on behavior and outcomes is needed to be fully helpful.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'The ID of the prop to clear'. The description adds no additional parameter semantics beyond this, but since schema coverage is high, the baseline score of 3 is appropriate as the schema adequately explains the parameter.

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 'Clear a specific prop from display' clearly states the action (clear) and target (prop), but it's somewhat vague about what 'clear' means in this context (remove from view? delete permanently?). It distinguishes from sibling tools like 'props_get' or 'props_set' by focusing on removal, but doesn't specify how it differs from 'clear_layer' or 'clear_trigger_group' which also involve clearing operations.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools involving clearing operations (e.g., 'clear_layer', 'clear_trigger_group', 'messages_clear'), the description doesn't indicate whether this is for props specifically versus other elements, or what prerequisites might exist (e.g., needing the prop ID).

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