policy_create_destination_list

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

The description explains that access and destination_type are recorded at creation and that entries can be added later or via initial_destinations. Although no annotations are present, it adequately covers creation behavior, though it could mention creation reversibility.

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, front-loaded with the purpose, and every sentence provides essential information. No fluff or repetition.

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 creation and entry addition methods but does not mention the return value (e.g., ID of created list). Given the tool's complexity and lack of output schema, this omission reduces completeness.

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 100% schema description coverage, the baseline is 3. The description adds value by explaining the relationship between access, destination_type, and the two ways to add entries, which enriches the schema-provided descriptions.

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 explicitly states 'Create a Destination List', providing a specific verb and resource. It distinguishes from sibling tools like policy_create_application_list by focusing on destination lists and mentioning entry addition via policy_add_destinations.

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 clearly indicates when to use this tool (to create a list) and mentions alternative tools (policy_add_destinations) for adding entries, guiding the agent on when not to use this tool for that purpose.

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