list_dlp_profiles

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

No annotations are present, so the description carries the full burden. It discloses that the operation is a read-only listing scoped to an account, but it does not mention pagination, response shape, permissions, or rate-limit considerations. The core behavior is minimally transparent but not detailed.

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 filler, front-loading the action and scope. Every word earns its place and there is no unnecessary elaboration.

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?

Given the low complexity, one fully documented parameter, and no output schema, the description is adequate for straightforward invocation. It lacks optional context like pagination or a pointer to get_dlp_profile for single-record needs, but these are not essential for a basic list call.

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?

The schema already documents account_id with 100% coverage, and the description adds no additional constraints, defaults, or format details. The baseline of 3 applies because the schema does the necessary work.

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 uses the specific verb 'List' with the resource 'DLP profiles' and the scope 'for an account,' clearly identifying the operation. It distinguishes itself from siblings like get_dlp_profile and list_dlp_datasets/list_dlp_patterns by naming a distinct resource and list-vs-get action.

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 only states what the tool does; it offers no guidance on when to choose it over alternatives such as get_dlp_profile for a single profile or list_dlp_datasets for related resources. No exclusions, prerequisites, or conditional context are provided.

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