set_phase_property

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

Annotations already indicate readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds that the operation is phase-scoped, which is useful context, but doesn't disclose additional behavioral details like whether the phase must exist or what happens on failure. Thus a moderate score.

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 two sentences, with the main action front-loaded and the contrast as a second sentence. Every word 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?

The description gives the core operation and a key distinction from set_property, and an output schema exists to cover return values. However, with 4 required parameters and no schema descriptions, the description leaves parameter semantics under-specified for a complete invocation. Moderate.

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 description must compensate for the four parameters. It only mentions 'property' and 'phase' implicitly via 'Set a property... for one specific phase only', but does not explain 'path' (object reference) or 'value' (new value type/format). Therefore it adds minimal parameter semantics.

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 uses a specific verb 'Set' with a clear resource 'property of an object' and scoping 'one specific phase only'. It explicitly names the sibling 'set_property' and contrasts the phase-scoped behavior, making the purpose unambiguous.

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 explicitly distinguishes this from set_property, saying 'distinct from set_property, which changes a property without phase scoping.' This tells the agent when to use this tool (when phase scoping is needed) and when not to (when not phase-scoped).

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