set_profile

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

No annotations are present, so the description must fully disclose behavioral traits. It mentions that profiles adjust sensitivity and blocked categories, but omits side effects like whether the change persists across sessions, if it requires special permissions, or if it is reversible. This is insufficient for a mutation tool.

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 two concise sentences with no redundant information. The first sentence states the action, the second explains the profiles and their effect. Every word earns its place.

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?

The tool is simple (1 parameter, no output schema). The description covers what it does and the meaning of the profiles. However, it does not mention the return value (e.g., confirmation message or new profile status), which would be helpful for completeness given the lack of an output schema.

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 input schema has 100% coverage (the parameter 'name' has a description), providing a baseline of 3. The tool description adds value by explaining that each profile adjusts scanner sensitivity and blocked categories, giving semantic meaning beyond the enum labels.

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 uses a clear verb ('Switch') and specific resource ('safety profile'), and lists all available values. It distinguishes the tool from siblings like 'get_profile' (which reads the current profile) and 'set_engine' (which configures a different aspect).

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 states the tool's purpose but provides no explicit guidance on when to use it versus alternatives (e.g., 'get_profile' for viewing, or when a profile change is needed before scanning). The use case is implied but not spelled out.

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