set_security_profile

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

No annotations are provided, so the description carries the full burden. It discloses that the tool changes the default configuration and that the effect is scoped to calls lacking an explicit profile. It also discloses the return value. It does not mention side effects or permissions, but for a configuration setter, this is adequate.

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 compact and front-loaded. The first sentence states the core purpose, followed by a clarifying sentence about when it applies, and then a well-structured Args/Returns section. Every sentence contributes value without fluff.

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 single-parameter setter with an output schema, the description covers the action, condition of applicability, parameter values, and return behavior. It is complete in context; no additional details are needed for the agent to use this tool safely and correctly.

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 only provides a string type with no description or enum. The description compensates by listing the allowed values: 'strict', 'balanced', 'permissive'. This is essential information for the agent to invoke the tool correctly and is not present in the schema.

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's action: 'Set the default security profile for script execution.' This is a specific verb+resource. It distinguishes itself from siblings by referencing execute_applescript and implying get_security_profiles is for retrieval, so there is no ambiguity.

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 explains when this setting applies: 'when no explicit profile is specified in execute_applescript calls.' This provides clear context for usage. It does not explicitly name alternatives or exclusions, but the context is sufficient for a simple setter.

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