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

Annotations already indicate readOnlyHint=true (read-only). The description adds valuable context: access restrictions for FREE businesses and dependency on check_business_tool_access. It does not contradict annotations.

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 front-loaded with the core purpose, followed by necessary usage instructions. It is relatively concise, though multiple sentences are used for preconditions. Every sentence adds value.

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 no output schema, and the description does not explain what the response contains (e.g., settings fields). It focuses heavily on access checks rather than the tool's function and return. Parameter explanations are 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?

Schema coverage is 0%, so description must compensate, but it does not mention any parameter details (action, communityId, videoProvider). CommunityId is implied but not explained. No parameter descriptions are provided.

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 'Get Magic Content generation settings for a community', which is a specific verb and resource. It distinguishes from sibling tools like get_magic_content by focusing on settings. However, it doesn't elaborate on what 'settings' includes, leaving some ambiguity.

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 explicit preconditions: check business permissions, FREE businesses cannot use, call check_business_tool_access before inputs, and handle grace-period warnings. This is comprehensive guidance on when and how to use the tool.

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