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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds a meaningful behavioral fact beyond those annotations: 'Sends require human approval,' which clarifies the human-in-the-loop requirement governing outbound sending.

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 the core resource and then gives two routing pointers plus an approval requirement in four short fragments. Every sentence earns its place, with no filler or redundancy.

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 policy tool with no parameters and an output schema, the description covers the key routing and approval context. It could be slightly more complete by explicitly stating that it returns the outbound gateway policy rules, but the title and output schema fill that gap.

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 tool has zero parameters and an empty object schema, so there is no parameter semantics to explain. Per the rubric, a zero-parameter tool receives a baseline of 4 when the schema requires no additional description.

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 opens with the noun phrase 'Outbound send rules,' which identifies the resource but does not state a verb such as 'read' or 'return.' It does distinguish related siblings by naming human_oversight_policy and prepare_outbound_invitation, but the core action remains implied rather than explicit.

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?

It gives clear routing guidance: 'General autonomy: human_oversight_policy' and 'Prepare: prepare_outbound_invitation,' which tells the agent which sibling to use for related needs. It also states the approval condition for sends, though it does not explicitly say 'use this tool when you need outbound send rules.'

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