set_content_control_value

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

Describes the write operation and provides checkbox value mapping, but lacks disclosure of error conditions (e.g., tag not found), side effects, or required permissions. With no annotations, more behavioral context is needed.

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?

Extremely concise: two sentences plus parameter list. Front-loaded with action verb and resource. Every sentence is necessary and informative.

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?

Covers input parameters adequately but omits prerequisites (e.g., document must be open, content control must exist) and does not mention output schema. Given output schema exists, description need not explain return values, but preconditions would improve completeness.

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?

Adds meaning to both parameters: tag explained as 'Tag name of the control to update', value detailed for checkbox. However, does not specify expected value formats for other content control types (e.g., plain text, dropdown). Schema has 0% coverage, so description partially compensates.

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?

Clearly states it updates the value/text of a content control by tag, distinguishing from general 'update_content_control' which likely updates other properties. However, does not explicitly differentiate from sibling 'update_content_control'.

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 on when to use this tool versus alternatives like 'update_content_control' or 'set_content_control_value' for other control types. No scenarios or exclusions provided.

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