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

Annotations only supply destructiveHint=true and a title, so the description carries the behavioral burden. It does echo the write nature ('WRITE') and the underlying endpoint (POST /api/v1/items), confirming a mutating create. However it says nothing about what happens on duplicate names, permission/plan requirements, or what the call returns (no output schema exists), leaving meaningful behavioral gaps.

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?

One dense, front-loaded sentence plus two short tags ('WRITE.', endpoint) — no filler, and the primary capability and its two modes come first. The telegraphic fragments are slightly terse but each earns its place by signaling mutation and the REST mapping.

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?

For a 15-parameter create tool with nested objects and no output schema, the description covers the item/folder distinction and folder nesting but omits several notable optional groups (photos, min_quantity, secondary barcode, label symbology) and never indicates what a successful create returns, such as the new item id. Structure is adequate but not complete for the tool's 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% across all 15 parameters, so the schema already documents name, type, parent_id, custom_attribute_values and the rest. The description merely summarizes a subset (quantity, price, tags, custom fields, barcodes, measured quantity) without adding format or validation detail beyond the schema, so baseline 3 applies.

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 opens with a specific verb+resource ('Create a trackable item ... or a folder') and immediately disambiguates the two type values, which no sibling tool covers. An agent can tell it apart from sortly_update_item, sortly_move_item and the get/list siblings without opening the 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?

Usage is implied by the description's scope ('Create ...'), and the nesting hint via parent_id gives one conditional behavior, but there is no explicit when-to-use vs when-not guidance and no named alternatives (e.g., update_item for modifications, move_item for relocation). Adequate but with clear gaps.

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