list_dlp_rules

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

Without annotations, the description explains the purpose (list all rules) and the type of data protected, but does not mention read-only nature, pagination, or limits. However, it is a simple read operation with no side effects, so transparency is adequate.

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 efficiently deliver the purpose and context without extraneous information. Every sentence adds value.

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 no parameters and an output schema present, the description fully explains the tool's function and the domain (DPR rules, browser actions). No gaps remain.

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?

There are zero parameters, and schema coverage is 100%. The description does not add parameter-specific meaning, but the baseline for 0 params is 4, and the tool is straightforward.

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 'Lists all Chrome DLP rules' with a specific verb and resource, distinguishing it from siblings like create_chrome_dlp_rule (creation) and get_dlp_rule (likely single rule retrieval).

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 for viewing all rules but provides no explicit guidance on when to use this tool versus alternatives like get_dlp_rule or search tools. No context on exclusions or prerequisites.

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