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

Annotations show readOnlyHint=false, aligning with 'generate' as a write operation. The description adds critical context about access prerequisites, permission checks, and prohibition when access is blocked, which goes beyond annotation information.

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 four sentences, relevant but somewhat verbose (e.g., 'Before offering this action or requesting its inputs'). Key info is front-loaded, but procedural details could be condensed.

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?

The tool has 12 parameters, no output schema, and moderate annotations. The description focuses heavily on access control but omits details on how generation works, parameter roles, output format, or required data. This is insufficient for a complex tool.

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 description coverage is 0% and the description provides no explanation of the 12 parameters. It only vaguely references 'selected prompt', which likely maps to creativeDirectionPrompt, but no detail on assetId, communityId, or other fields.

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 clearly states 'Generate a Magic Content asset from a selected prompt', specifying a verb and resource. It distinguishes from siblings like generate_magic_content_from_scratch and edit_magic_content by implying a predefined prompt. The scope is unambiguous.

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 explicitly instructs to check business permissions before use, names check_business_tool_access, warns about FREE restrictions, and tells how to handle grace-period warnings. It provides clear when-to-use and when-not-to-use guidance.

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