wb_pass_create

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

With no annotations, the description carries the behavioral disclosure burden. It does add one useful behavioral fact: the generated pass is valid for 48 hours. However, it does not disclose side effects, approval requirements, return value, or prerequisites such as office validity.

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 a single compact sentence with the key fact front-loaded. The parenthetical '(создать пропуск)' is somewhat redundant with the English clause, but it does not significantly bloat the description.

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 has no output schema and no annotations, and the description does not mention the response format, required permissions, or how to discover legitimate office IDs. For a mutation tool with 5 required parameters, this is under-specified and would leave an agent guessing about important call context.

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 0%, and all 5 required parameters lack descriptions. The description names none of the parameters—first_name, last_name, car_model, car_number, or office_id—so an agent receives no help understanding what values are expected or what office_id refers to.

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 and resource: 'Create a warehouse pass'. This clearly distinguishes it from sibling tools like wb_pass_update, wb_pass_delete, and wb_passes_list, and the validity duration adds useful specificity.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that wb_pass_update should be used for modifying an existing pass or that wb_passes_offices might need to be consulted first to obtain a valid office_id.

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