sophos_list_cloud_security_profiles

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

Description states 'list all' and 'latest versions', indicating read-only behavior and versioning. However, with no annotations, it does not disclose authentication needs, rate limits, or potential side effects. Minimal behavioral context beyond the operation itself.

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?

Single sentence with a clarifying follow-up. Concise and front-loaded with the core purpose. No unnecessary words, but could be structured more formally.

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?

Describes purpose and profile definition briefly, but lacks information about response structure, pagination handling, or return value details. Output schema is absent, so description should cover these gaps. Adequate but not complete.

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 has 100% coverage with descriptions for all 4 parameters. Description adds 'latest versions' context but no additional parameter-specific details. Baseline 3 is appropriate as schema does the heavy lifting.

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 the verb 'list', resource 'cloud security runtime detection profiles', and scope 'for a tenant (latest versions)'. It distinguishes from sibling tools like 'sophos_get_cloud_security_profile' and 'sophos_list_cloud_security_default_contents' by specifying listing all profiles and returning latest versions.

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?

No guidance on when to use this tool versus alternatives such as 'sophos_get_cloud_security_profile' or 'sophos_list_cloud_security_default_contents'. Does not specify when not to use or provide context for selection.

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