post_w_asset_assets

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

With no annotations, the description carries the full burden of behavioral disclosure. It signals mutation through 'Create' and 'POST,' but does not mention authentication requirements, idempotency, side effects on existing assets, or failure modes. The endpoint and parameter placement details are structural rather than behavioral.

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 short sentences with no filler. The main action is front-loaded, and each clause adds useful routing information about one or more parameters.

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?

Despite having an output schema, the description lacks the specific header names, route ID values, body fields, and auth context needed to invoke the endpoint reliably. It covers parameter placement but leaves the actual API contract to external knowledge, which is a significant gap for a tool with no annotations and no schema-level property documentation.

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?

The input schema has four opaque anyOf object properties with zero property descriptions (0% coverage). The description compensates by assigning a clear semantic role to each parameter: route IDs in path_params, filters/pagination in query, required headers in headers, and the payload in body. It still omits specific key names and required body fields, but it adds substantial meaning beyond the bare schema.

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 the concrete verb and resource, 'Create asset,' and ties it to the exact endpoint, `POST /w/asset/assets`. This clearly identifies it as the create operation and distinguishes it from sibling patch/delete/get asset tools, though it does not explicitly name those alternatives.

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 sibling tools such as patch_w_asset_assets or delete_d_asset_assets_id. It explains how to distribute inputs across path_params, query, headers, and body, but not what conditions should trigger this choice or when it should be avoided.

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