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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the return value is a JSON Schema, but it does not describe schema versioning, content scope, or how the schema relates to downstream carousel authoring tools. No annotation contradiction.

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?

The description is a single front-loaded sentence with no wasted words. It directly states the return value and resource scope.

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 zero-parameter schema-retrieval tool with annotations covering safety and no output schema, the description is mostly complete: it states that a JSON Schema for carousel decks is returned. It could be slightly stronger by clarifying how this schema is used with scaffold_carousel_deck or listing templates, but that is a minor gap.

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?

This tool has zero parameters, so the baseline is 4. The empty input schema is appropriate, and no additional parameter guidance is needed.

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 states a specific verb and resource: return the JSON Schema for Instavar carousel decks. It distinguishes the resource from the sibling get_video_schema by specifying carousel decks rather than video. It does not explicitly contrast with other carousel-related siblings like list_carousel_templates or scaffold_carousel_deck.

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 implies usage for retrieving the carousel deck schema, likely before scaffolding or validating a deck, but it does not explicitly state when to use it versus get_video_schema, get_template, or scaffold_carousel_deck. There are no exclusions or alternative-routing instructions.

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