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

The annotations are comprehensive (readOnlyHint, destructiveHint, idempotentHint) and carry the heavy lifting for behavioral disclosure. The description adds no significant new information regarding constraints or mutations.

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 perfectly concise, using a single, direct sentence that front-loads the core function and topic.

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 list operation involving pagination, the description is incomplete as it does not mention or reference the existence of limit and offset controls, which are crucial input behaviors.

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?

With 0% schema description coverage, the description fails entirely to add semantic meaning to the two input parameters, 'limit' and 'offset'. It provides no context on how these parameters function for pagination.

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 resource being handled ('automatic policy-assignment rules') and the action ('Read'), successfully distinguishing it from a general policy retrieval tool like 'get_policy'. It is very specific about the scope of the data.

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 offers no guidance on when to use this tool versus alternatives like 'list_policies' or 'get_policy_assignment', nor does it specify if the rules are global or scoped to a workspace.

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