name_output_schema_major_version

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

No annotations provided, so description carries full burden. Discloses that the operation is a rename only, non-destructive, and does not affect creation, publishing, or rollback. Sufficiently transparent for a simple metadata mutation.

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 sentences, each serving a distinct purpose: stating the main action and clarifying limitations. No unnecessary words.

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?

Given simple input schema (3 required fields, no output schema), the description fully explains the tool's purpose, parameters, and boundaries. No gaps.

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 coverage is 100%, so baseline is 3. Description adds significant value by clarifying that majorVersion is an integer from list_output_schema_versions, and that name is the new name. No ambiguity.

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?

Clearly states the verb 'name' and resource 'output_schema's major version'. Distinguishes from sibling naming tools by specifying the resource type. Includes context 'label a release so it is easy to find in history'.

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?

Explicitly clarifies what the tool does not do ('does not create, publish, or roll anything back') and specifies target ('MAJOR version by its integer number, not a checkpoint or a versionId'). Provides good context for when to use, though does not explicitly compare to alternatives.

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