background_asset_versions_create_instance

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about auth requirements, what gets created, side effects, or the response. Its only substantive content is a pointer to the request envelope schema, which is a payload hint rather than behavioral context.

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?

It is short but wasteful: the 'POST /v1/backgroundAssetVersions' string is printed twice, and the remaining text is a schema cross-reference with no front-loaded explanation of intent.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits required JSON:API envelope structure, auth expectations, and any expectation about the created resource, leaving the agent to open an external OpenAPI spec.

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%, so the single body parameter is documented in the schema. The description only echoes that the body follows the BackgroundAssetVersionCreateRequest JSON:API envelope, adding no parameter meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 is essentially a route restatement: 'POST /v1/backgroundAssetVersions'. The HTTP verb implies creation of a background asset version, but there is no plain-language statement of what the tool does, no scope, and no differentiation from the many sibling create_instance tools. It borders on tautology with the tool name.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the large set of sibling create tools. The agent is given no basis for choosing this tool over others.

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