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

Annotations only signal a non-read-only, non-idempotent, non-destructive write; the description goes well beyond that by stating the review widget renders immediately, nothing is generated, no credits are charged, and no sign-in is required. Those are precisely the side-effect and auth facts the schema cannot express.

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?

Front-loads the purpose, then the prompt convention, then side effects, then routing exclusions — each sentence adds distinct information with no filler. The length is justified by the amount of routing and side-effect detail packed in.

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 return values need not be described, and the description covers the remaining gaps: no-credit/no-generation behavior, immediate widget rendering, no-auth, and precise routing against all relevant siblings. Nothing an agent needs in order to call this correctly is missing.

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?

With 0% schema description coverage, the description must carry the load and does so well for the required 'prompt' (prescribing the logo-brief content and the exact style suffix). However, count, ratio, duration, resolution, model_id, model_name, and advanced_params get no meaning or guidance at all, leaving most of the surface undocumented.

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+resource ('Prepare a ManyMotions Logo Maker project') and immediately scopes it to text-to-image logo designs from a brand brief, which cleanly separates it from siblings like generate_logo and update_logo_project. An agent can tell what it does and does not do without opening the 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?

Explicitly enumerates both sides: use only for new text-to-image logo designs from a brief, and do not use for uploaded/reference images, editing an existing logo, SVG/vector export, background removal, video, or trademark checks. This is exactly the when/when-not/alternatives routing the dimension asks for.

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