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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose permission/entitlement requirements, whether a new rule overrides existing ones or how precedence works, whether it takes effect immediately, or what happens if a rule for the domain already exists.

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 tight sentences with the what/where front-loaded and the enum semantics second. Zero filler or restated boilerplate.

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?

A mutation tool with no annotations and no output schema needs to carry its own safety/permission context. The description covers the create action and enum semantics adequately but omits precedence, idempotency/duplicate behavior, and authorization requirements.

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 coverage is 100%, so all four parameters (profile_id, kind, domain, note) are already documented in the schema, including the enum meaning. The description's restatement of kind=allow/deny adds nothing beyond the schema's own enum description, and the optional note parameter is never mentioned.

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?

States a specific verb (Create) and resource (custom allow/deny rule) plus scope (for a domain on a profile). An agent can immediately distinguish it from delete_rule, list_rules, and create_schedule without opening any schema.

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 second sentence explains how to use the kind enum (deny to block, allow to permit), which is invocation guidance rather than tool-selection guidance. It never says when to reach for create_rule instead of simulate_policy to test a rule first, nor when-not to use it (e.g. duplicates, managed domains).

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