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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond annotations: Sparka ships no script library, the deck's own code is the integration, the reference code's look can be adapted, and no account key is required.

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 front-loaded with the core purpose and then enumerates the covered topics. The first sentence is long and dense, but the enumeration is relevant for a guide tool and every clause contributes useful scope 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?

An output schema exists, so the description need not explain return values in detail. Annotations cover the safety profile. The main gap is the unexplained 'part' parameter, but otherwise the description gives enough context for an agent to understand what the tool provides.

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?

The input schema has one parameter, 'part', with an enum of all/rules/reference_code/html_skeleton, but schema description coverage is 0%. The description never mentions this parameter or explains that the guide can be requested in parts, so it fails to compensate for the missing schema documentation.

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: it returns the rules and a reference JavaScript pattern for making an HTML presentation interactive with Sparka. It clearly distinguishes this guide tool from the sibling CRUD tools for accounts, presentations, questions, and results.

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 makes clear this is the integration guide for building an interactive deck, and notes that no account key is needed. It does not explicitly name alternatives or when-not-to-use conditions, but the context is sufficiently clear for an agent to select it over the sibling tools.

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