Set Profile Parameter

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the mutation safety profile. The description adds no extra behavioral context beyond repeating the action, such as permission requirements or effects on other parameters; it neither contradicts nor enriches the 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?

A single, direct sentence with no fluff. It is front-loaded with the verb and resource, efficiently conveying the core operation.

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?

For a simple setter with high schema coverage and annotations, the description adequately conveys the purpose. It could mention explicit alternatives or conditions (like 'use obs-get-profile-parameter to read'), but given the simplicity and structured context, it is nearly 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?

Schema description coverage is 100%, with each of the three parameters having a clear description (including the null-for-delete semantics on parameterValue). The tool description adds no additional parameter meaning beyond the schema, so the baseline of 3 applies.

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 action (Sets) and the specific resource (a parameter in the current profile's configuration). It distinguishes from sibling tools like obs-get-profile-parameter and other set tools by referencing 'profile's configuration' precisely.

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 implies usage by its action and resource, but does not explicitly state when to use it versus alternatives (e.g., when to use obs-get-profile-parameter or other setter tools). No exclusions or alternative tool references are provided, leaving the agent to infer from the name alone.

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