create-policy

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Create a new policy.' with no information about idempotency, conflict behavior, required policy fields, or side effects. This adds no value beyond the tool name.

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 extremely short (five words) and clear, but it omits essential information. It is concise but under-specified, not fitting the spirit of conciseness where every sentence earns its place; here the single sentence adds minimal value.

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 tool creates a policy within a large API domain with many policy operations. The description provides no explanation of what a policy is, what the policy object must contain, or any constraints. With no output schema and minimal schema description, the description is completely inadequate for the complexity.

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 100% because the only parameter, 'policy,' has a description ('Policy object.'). The tool description adds no further parameter meaning. Per baseline, score 3 when schema covers the parameter descriptions, though the description is very generic.

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 uses a specific verb+resource ('Create a new policy'), making it clear the tool creates a policy. However, it does not distinguish from sibling tools like create-policies-bulk or update-policy, so it lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives like create-policies-bulk or update-policy. The description provides no context for selection criteria or prerequisites.

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