list_dlp_profiles

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the return structure, error-message behavior, and the ADOM default source, but it does not describe permissions, pagination, or other operational constraints for the listing operation.

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 front-loaded with a single clear purpose sentence, followed by concise argument and return sections. It is appropriately sized, though the return-value listing duplicates information already available in the output schema.

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 read-only listing tool with two optional parameters and an output schema, the description provides enough context about parameters and return shape. Missing explicit usage guidance and pagination details are minor gaps.

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 description coverage is 0%, so the description must compensate. It does so for both parameters: adom is explained as defaulting from DEFAULT_ADOM or 'root', and name_filter is documented as a partial-match filter.

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 states a specific verb and resource: 'List DLP (Data Loss Prevention) profiles in an ADOM.' This clearly distinguishes it from sibling tools like get_dlp_profile, create_dlp_profile, update_dlp_profile, and delete_dlp_profile by its listing scope.

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?

Usage is implied by the verb 'List' and the presence of an optional name filter, but the description does not explicitly say when to use this tool versus alternatives such as get_dlp_profile or list_dnsfilter_profiles. No exclusions or alternatives are named.

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