app_screenshots_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: not that this is a mutation, not the asset-upload/reservation flow typical for screenshots, not auth requirements, and not whether the call is idempotent or reversible. It is effectively a bare endpoint pointer.

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 the parenthetical '(POST /v1/appScreenshots)' duplicates the sentence opening verbatim, so the text is wasteful rather than concise. Front-loading a redundant verb+path leaves no room for actual information.

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?

This is a write/create tool with no annotations, no output schema, and only a free-form envelope body, so the description must carry the load; instead it says almost nothing. An agent cannot know the required relationship (screenshot set), the envelope structure, or side effects from this definition alone.

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?

With 100% schema description coverage the baseline is 3, but the description adds zero incremental meaning over the schema, which already states 'Shape: components.schemas.AppScreenshotCreateRequest.' It merely parrots the same schema reference without clarifying the unconstrained body object (additionalProperties: {}) or the required JSON:API envelope fields.

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 only restates the HTTP verb and path ('POST /v1/appScreenshots'), repeating it twice. It never explains what an app screenshot is in this API's domain, nor how this create differs from siblings like app_screenshots_update_instance or app_screenshot_sets_create_instance. An agent must infer meaning entirely from 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 (e.g., needing an existing AppScreenshotSet to attach to), and no mention of alternatives or the upload flow. Nothing routes the agent between this tool and its many sibling create tools.

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