update_parameter_advanced

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

With no annotations, the description carries full burden. It discloses that the tool toggles boolean flags, that allow_null writes <Nullable>, and that no flags results in a no-op. It does not mention prerequisites like needing an editing transaction or required permissions, but the behavioral details given are sufficient for safe invocation.

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 extremely concise: two sentences covering all essential details. The first sentence lists the flags; the second clarifies no-op behavior and distinguishes from cascading parameters. No unnecessary words.

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 moderate complexity (four boolean flags), no output schema, and no annotations, the description is complete enough. It explains all parameters, provides usage guidelines, and addresses common confusion about cascading parameters. An agent can confidently use this tool based on the description alone.

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 description adds significant meaning beyond the raw schema, which has 0% description coverage. It explains each boolean flag's purpose (e.g., allow_null writes <Nullable>) and mentions that name and path are required. This compensates fully for the schema's lack of descriptions.

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 toggles four specific boolean flags (multi_value, hidden, allow_null, allow_blank) on a report parameter. It lists each flag and distinguishes itself from sibling tools by explicitly noting that cascading parameters are not a flag and directing to alternative tools, 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 says 'Each is independently optional. With no flags passed it's a no-op.' This provides clear guidance on when to use the tool (to toggle these flags) and when not to (for cascading parameters), naming specific alternative tools. This effectively helps in tool selection.

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