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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds non-obvious operational context the annotations cannot: the response is long markdown and should be cached for the session. It does not discuss failure modes, but for a static guide tool there are few to disclose.

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 tightly packed clauses: what it returns, when to use it versus the sibling, and the caching instruction. Purpose and routing guidance are front-loaded, and no sentence is redundant.

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?

No output schema exists, and the description compensates by characterizing the return value's shape and size (long markdown covering layouts, components, MDX and click syntax). Combined with the sibling routing and caching advice, an agent has everything needed to call it correctly once.

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?

Zero parameters, so the baseline is 4; the description correctly confirms 'no arguments,' matching the empty schema. There is nothing further to document on the input side.

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?

Specific verb+resource ('Return the guide to writing a Kadal Deck') with the contents enumerated: talk shaping, layouts/components overview, and full MDX and click syntax. It explicitly contrasts itself with the sibling deck_reference, so the agent can distinguish the two without opening either schema.

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?

States exactly when to call it ('once before drafting or editing a deck.mdx') and names the alternative plus the condition that selects it ('use deck_reference instead to look up one component, layout or option in detail'). It even specifies call frequency — once per session, not per slide.

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