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

Adds important behavioral details beyond annotations: business permission checks, free tier restriction, grace-period warnings, and the instruction to never proceed when blocked. Annotations already indicate read-only, and description aligns without contradiction.

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 concise (~60 words) and front-loaded with the core purpose. Every sentence adds value, though it could be slightly more structured (e.g., separate preconditions).

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?

Missing crucial details: no parameter descriptions, no output description (no output schema either), and pagination parameters are unexplained. The description covers permission context but leaves the agent guessing on how to call the tool and what to expect.

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% (no parameter descriptions in schema), and the tool description does not explain any of the four parameters (communityId, assetType, pageNo, pageSize). The agent receives no guidance on parameter values or formats.

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 the exact action ('List') and resource ('Magic Content style presets') with scope ('for a community'), clearly distinguishing it from sibling tools like list_magic_contents or list_magic_content_versions.

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?

Provides clear context: check business permissions, FREE businesses cannot use, call check_business_tool_access, and show warning/links. Does not explicitly compare to alternatives but gives strong preconditions for safe usage.

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