sophos_create_endpoint_group

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

Annotations provide readOnlyHint=false and destructiveHint=false, so description correctly confirms this is a write operation. Description adds context about grouping endpoints by type, but does not disclose potential side effects (e.g., whether creating a group triggers policy enforcement) or any prerequisites.

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 sentences: the first states the action, the second provides purpose. No redundant information. Perfectly sized and front-loaded.

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 creation tool, description explains purpose and type enum. However, it omits information about the return value (e.g., does it return the created group?) and any constraints like uniqueness of group names. Still, it addresses the key context for an AI agent.

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?

All 4 parameters have descriptions in the schema (100% coverage). The description adds no additional parameter-specific details beyond what the schema already provides, so baseline score is appropriate.

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?

Description clearly states 'Create a new endpoint group in a tenant' and explains that groups organize endpoints by type for policy assignment. This specific verb-resource combination distinguishes it from sibling tools like sophos_get_endpoint_group or sophos_list_endpoints.

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 when a new group is needed and mentions policy assignment, but does not explicitly state when to use this tool versus alternatives (e.g., when to update an existing group instead). No 'do not use if' guidance or alternatives are listed.

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