List policies

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

Annotations already declare readOnlyHint=true, and the description confirms it only lists policies. The description adds the exact return structure but no additional behavioral traits like permission requirements or potential delays.

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 that efficiently communicates the tool's purpose and return structure. It is front-loaded with the core function, though the detailed return object description could be more structured.

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 description covers the return object in detail, which is sufficient for a read-only tool with annotations. It lacks information on error handling or empty results, but the context signals indicate no output schema is provided in the definition, so the description fills that gap adequately.

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 33% (only 'database' described). The description mentions 'schema' and 'table' but does not elaborate on their meaning or constraints beyond what the schema provides. It partially compensates by naming the parameters, but not enough to raise the score.

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 the tool lists Row-Level-Security policies on a table and whether row security is enabled, specifying the exact verb 'list' and resource 'policies on a table'. It distinguishes from sibling tools by its specific focus on RLS policies.

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 inspecting RLS policies but does not explicitly state when to use it versus alternatives or when not to use it. No guidance on prerequisites or context is provided.

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