Set Property

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating a mutation operation. The description adds the coercion behavior ('Coerces lists → Vector for Vector properties; other values pass through'), which is useful. However, it doesn't disclose potential side effects (e.g., whether property changes persist immediately, or if there are any restrictions on property types). The description adds some value beyond annotations but could be richer.

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 succinct and front-loaded, with two sentences: the first clearly states the action, and the second adds a behavioral detail. No wasted words; it's efficient and to the point.

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 mutation tool with no output schema and 3 undocumented required parameters, the description is under-specified. It doesn't explain the 'handle' parameter meaning or format, potential error conditions, or the result of the operation. The coercion note is helpful, but overall, an agent may not be able to call this correctly without additional context.

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 description coverage is 0%, so the schema provides no descriptions for the parameters. The description explains the 'value' parameter's coercion behavior, but does not explain 'handle' or 'name' semantics. Given that there are 3 required parameters with zero schema coverage, the description partially compensates but leaves significant ambiguity, especially for 'handle' which likely references an object in the system.

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 states a specific action ('Set a single property by name on an object') with a clear verb and resource. It distinguishes from siblings by focusing on 'single property' and 'by name', which is consistent with the tool name. However, it doesn't explicitly differentiate from other property-related tools like set_visibility, but the description is clear enough for basic identification.

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 does not provide any guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., object must be selected, handle must be valid), no exclusions, and no comparison to sibling tools. The agent is left to infer usage from the name and schema, which is inadequate for a tool with a handle parameter that likely requires specific context.

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