set_parameter_prompt

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

The description discloses that an empty string clears the element entirely, and a space leaves it blank but present, which is key behavioral information. Without annotations, the description carries the full burden, and it provides useful mutation details.

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 with two sentences that are front-loaded and directly communicate the action and special behaviors. 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?

While the description adequately covers the core operation and prompt behavior, it lacks context on how 'name' and 'path' are used and does not explain the return value or side effects. For a simple setter, it is minimally complete.

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 meaning only for the 'prompt' parameter (empty vs space), but does not explain the 'name' and 'path' parameters. Since schema coverage is 0% and there are three required parameters, the description should compensate more.

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 specifies the verb 'Write' and the resource '<Prompt> text on a ReportParameter', making the action clear. It distinguishes itself from sibling parameter tools by focusing specifically on setting the prompt text.

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 states when to use an empty string to clear and a single space for blank-but-present, giving clear guidance on input values. However, it does not provide context about when to use this tool versus other parameter-setting siblings.

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