set_parameter_default_values

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

Description thoroughly details behavior for each source type, including clearing behavior and that query mode uses only ValueField. However, it does not disclose side effects, permissions, or error conditions, which would be necessary without annotations.

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?

Single paragraph is dense but clear; front-loads purpose. Could be broken into bullet points for readability, but no wasteful sentences.

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 main behavior but lacks details on return values (only mentions 'returns cleared=true' for clear case) and prerequisites like editing mode. With no output schema and 6 params, more completeness would be 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?

Schema has 0% description coverage but description adds significant meaning: explains how source, static_values, and query_value_field interact. Common params like name and path are not described but are standard. Compensates well for low schema coverage.

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 sets or clears the DefaultValue on a report parameter, with detailed behavior for static vs query sources. It distinguishes from sibling tools like set_parameter_prompt.

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?

Usage is implied but not explicitly stated; no guidance on when to use this tool versus alternatives such as set_parameter_available_values or set_parameter_prompt. No exclusion criteria given.

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