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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write profile is already covered. The description adds genuine behavioral value beyond that: the upsert-in-place semantics and the fact that URL saves replace existing contents while inline saves always create new. It omits any auth/permission requirements and return behavior, but the output schema covers returns.

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?

Three sentences, front-loaded with the core action, then the input forms, then the key upsert distinction. Every sentence carries a distinct fact with no repetition or filler.

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 write tool with a rich nested auth schema, a 100% schema coverage and an output schema, the description supplies the crucial create-vs-upsert behavior. It stops short of the one thing an agent still needs: how it relates to the sibling update_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 schema already documents spec, name, websiteOrigin and the nested auth object. The description's note that a spec may be a URL or inline largely restates the schema's own spec description, so it adds little beyond the structured fields. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Store an OpenAPI/Swagger spec and its associated auth configuration') and scope (URL or inline). It is clear against read siblings like get_spec, but it never distinguishes itself from the sibling update_spec, leaving the save-vs-update boundary ambiguous.

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 through the upsert explanation (same URL reuses specId, inline creates new), which helps an agent predict the effect of a call. However, there is no explicit when-to-use guidance and no reference to the update_spec sibling, so the agent gets no help choosing between the two write tools.

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