create_package

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

The description adds significant behavioral context beyond annotations: it explicitly states 'MUTATING', 'Set dryRun=false to create', and 'Async operation'. Annotations only indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description enriches the agent's understanding without contradiction.

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 concise (two sentences plus a short note) and front-loaded with the core action. Every sentence adds value without 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?

Given the tool's complexity (7 parameters, 3 required, async) and no output schema, the description covers the creation action, async behavior, and dryRun mode. However, it omits details about the return value (likely a task), which would improve 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?

Schema coverage is 100%, so baseline is 3. The description reiterates the dryRun parameter's role but doesn't add meaning beyond the schema. No other parameters are elaborated, making the description's contribution minimal.

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 action ('creates a package') and the resource ('package from selected resources in a Cognigy.AI project'). It also explains the bundling purpose, distinguishing it from sibling tools like list_packages or delete_package.

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 provides explicit guidance: it is mutating, dryRun=false is required for actual creation, and the operation is async. This helps the agent understand when to use this tool, though it doesn't list alternatives or when not to use it.

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