sophos_create_policy

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the action and parameters, missing details on side effects, permissions required, reversibility, or what the response looks like. 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?

Two concise sentences, no wasted words. The key information (verb, resource, required/optional params) is front-loaded. It earns its length.

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?

Despite well-described parameters, the description lacks output information, error handling, prerequisites, and post-creation behavior. For a creation tool with no output schema or annotations, this is incomplete and leaves the agent guessing about the result.

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 coverage is 100%, so baseline is 3. The description summarizes parameters and adds a useful hint about using sophos_get_policy for the settings format. However, it does not explain each parameter beyond what the schema already provides, so no significant added value.

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 verb 'Create' and the resource 'endpoint policy', and distinguishes from sibling tools like sophos_clone_policy or sophos_update_policy by specifying it is for new policies and listing the required and optional parameters.

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 listing required fields, but does not explicitly state when to use this tool versus alternatives like sophos_clone_policy or sophos_update_policy. It provides a hint to use sophos_get_policy for the settings format, which partly guides usage but lacks explicit when-to-use or when-not-to-use context.

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