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

Annotations are minimal (readOnlyHint false, destructiveHint false, openWorldHint false). Description adds behavioral context about permission checks and access restrictions. However, it does not disclose that the upload is initiated asynchronously or that status can be checked via get_magic_audience_video_upload_status. No contradiction with 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?

Description is four sentences, front-loaded with purpose. Permission instructions are critical but could be formatted as a note or bullet. Overall concise and no redundant information.

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?

Tool has 2 required params, no output schema, and sibling tools include get_magic_audience_video_upload_status. Description covers access restrictions and preconditions but does not explain that upload is initiated asynchronously or mention subsequent status checking. Adequate but with a gap in workflow context.

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 has two parameters (videoLink and communityId) with 0% schema description coverage. Description provides no additional meaning about these parameters beyond what the schema types imply. For a tool with low schema coverage, the description should compensate but 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?

Description clearly states 'Start Meta video upload for a Magic Audience video link' – specific verb and resource. No explicit differentiation from siblings, but the tool is distinct enough given the context of video upload for Magic Audience.

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 instructions: check business permissions first, FREE businesses cannot use, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, never proceed when access blocked. Covers when to use, when not to use, and preconditions.

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