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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it details the exact return payload, the carousel body convention (slides joined by '\n\n---\n\n'), what is deliberately excluded, and what the returned url does. That is rich behavioral context an agent cannot derive from the annotations alone.

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?

A single front-loaded paragraph that leads with the core action and then groups returns by category; every clause carries information. It is on the dense/long side, but there is no filler to cut.

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?

With no output schema, the description carries the full burden of describing returns and does so thoroughly, including the carousel edge case and the reference/generation counts. An agent can call this confidently based on the description alone.

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 0% and the description never explains either parameter. 'by id' weakly implies contentId, but the optional brandId is completely undocumented – no format, no reason it is optional when contentId is required, no scoping effect. With zero schema descriptions the description had to compensate and does not.

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 and resource ('Get one content card's full detail by id') and then enumerates exactly which sections come back (script, planning fields, webSearch, counts). This clearly separates it from list_contents (single-card vs collection) and from the reference/generation history tools, which it explicitly excludes.

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 only implied: 'by id' and the note that it omits full reference, generation and refinement-history records loosely point the agent at list_content_references/list_content_generations, but no sibling is named and there is no explicit when-to-use or when-not-to-use statement. The 'opens the card in Dalea for review and editing' line hints at a review workflow but doesn't formalize it.

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