sophos_get_software_package

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the tool retrieves details, but omits information about authentication, rate limits, error handling (e.g., what happens if the package ID is invalid), or result format. This is insufficient for a read operation with no schema coverage for behavior.

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 a single sentence with no unnecessary words. It is front-loaded and efficient, conveying the essential purpose without filler.

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 (get by ID) and has high schema coverage, but there is no output schema to describe the response. The description does not mention what details are returned, error conditions, or pagination. While the tool is straightforward, the description lacks completeness for an agent to fully understand the behavior.

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% (both parameters described in input schema). The description mentions 'by ID' but does not add extra meaning beyond the schema's description of 'package_id'. Baseline of 3 is appropriate since the description provides no additional semantic value beyond 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 'Get details for a specific static software package by ID.' It uses a specific verb ('Get'), a resource ('static software package'), and a unique identifier ('by ID'), which distinguishes it from sibling tool 'sophos_list_software_packages' that retrieves all packages.

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 you need details of a single package), but it does not explicitly state when to use this tool versus alternatives like 'sophos_list_software_packages' or 'sophos_add_software_package'. No exclusions or context-specific guidance is provided.

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