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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's polling behavior, including conditions for free vs. paid audits and handling of pending states. However, it doesn't mention error handling, timeout limits, or authentication requirements, leaving some behavioral aspects unspecified.

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 extremely concise and front-loaded, consisting of just two sentences that efficiently convey the tool's purpose and critical usage guidelines. Every word earns its place, with no redundant information or unnecessary elaboration.

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?

Given the tool's polling complexity and lack of annotations/output schema, the description does well by explaining the polling logic and conditions. However, it doesn't describe what the status response looks like or potential error states, which would be helpful for an agent to interpret results. The completeness is good but not perfect for a polling 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?

The schema description coverage is 100%, with the single parameter 'auditId' well-documented in the schema as 'The audit ID returned from run_aeo_audit'. The description doesn't add any additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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 the verb 'check' and resource 'status of an AEO audit', making the purpose specific. It distinguishes from siblings by focusing on audit status rather than content suite operations (like generate_aeo_content_suite) or running audits (run_aeo_audit).

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 provides usage guidance: 'Poll until free_preview_ready (free) or is_complete at full report (paid). If paid_pipeline_pending is true, keep polling.' This tells the agent when to use this tool (for polling audit status) and provides specific conditions for continuing polling, which is crucial for understanding its role versus alternatives.

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

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

No annotations provided, so description carries full burden. It discloses key behavioral traits: polling nature, timing interval (15-30s), continuation until terminal states (completed/failed), and authentication requirement (same X-API-Key as generate). However, it doesn't mention rate limits, error handling, or what 'completed' or 'failed' entail. Good but not exhaustive.

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?

Two sentences, zero waste. First sentence states purpose and polling cadence. Second sentence adds auth detail. Front-loaded with essential info (polling, timing, termination). Every sentence earns its place by providing critical usage context.

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?

No output schema, so description should ideally cover return values, but it doesn't. However, given the tool's simplicity (1 param, no annotations), the description is largely complete: purpose, usage, auth, and parameter context are clear. Minor gap in not explaining status outcomes (what 'completed' or 'failed' mean), but overall sufficient for agent use.

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 100% (orderId documented), so baseline is 3. The description adds value by explaining orderId's origin ('returned from generate_aeo_content_suite'), providing context beyond schema. It doesn't detail format or constraints, but the linkage to generate is helpful. Scores above baseline for meaningful addition.

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 the tool's purpose: 'Poll Content Suite generation' - a specific verb (poll) and resource (Content Suite generation). It distinguishes from siblings by referencing generate_aeo_content_suite and contrasting with download_aeo_content_suite_zip (polling vs. downloading). The description goes beyond the name/title to explain what polling entails.

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?

Explicit guidance on when to use: 'After generate_aeo_content_suite returns (HTTP 202), call every 15–30s until status is completed or failed.' Clear timing, prerequisites, and termination conditions. It distinguishes from check_aeo_audit_status by focusing on Content Suite rather than audit, and from download_aeo_content_suite_zip by specifying polling precedes downloading.

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

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

With no annotations provided, the description carries the full burden. It discloses that the tool saves files to specific directories (cwd or AGENTAEO_MCP_DOWNLOAD_DIR) and requires the same API key as 'generate', which adds useful context. However, it doesn't mention potential errors, file size limits, or authentication requirements beyond the API key reference.

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 appropriately concise with two sentences that each serve a clear purpose: first stating the action and prerequisites, second describing the output behavior. It could be slightly more structured but wastes no words.

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?

For a download tool with no annotations and no output schema, the description provides adequate but minimal context. It covers the prerequisite state and output location, but doesn't explain what happens on failure, file format details, or return values. Given the tool's relative simplicity, this is minimally sufficient.

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 100%, so the schema already fully documents both parameters. The description doesn't add any meaningful parameter semantics beyond what's in the schema descriptions, so it meets the baseline of 3.

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 the action ('Download') and resource ('Content Suite ZIP'), and distinguishes it from siblings by referencing the 'generate' tool. However, it doesn't explicitly differentiate from 'check_aeo_content_suite_status' which is about status checking rather than downloading.

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 provides clear context for when to use this tool ('after status is **completed**') and references the prerequisite 'generate' tool. It doesn't explicitly state when NOT to use it or name alternatives, but the context is sufficiently clear.

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

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

With no annotations provided, the description carries full burden and does well: it discloses the async behavior (returns in seconds with orderId), typical completion time (5-25+ min), polling interval (15-30s), authentication requirement (AGENTAEO_API_KEY), and admin bypass conditions. It doesn't mention error handling or rate limits, but covers key operational traits.

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 appropriately sized and front-loaded with the core purpose. Every sentence adds value: async behavior, polling instructions, authentication, and admin bypass details. It could be slightly more structured but avoids redundancy.

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?

Given the complexity (async operation with polling) and no annotations/output schema, the description is mostly complete: it covers purpose, usage, behavior, and parameter context. It lacks details on error responses or output format, but provides enough for an agent to use the tool effectively with the schema.

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 100%, so the baseline is 3. The description adds some context: it clarifies that orderId comes from 'aeo_content_orders after $499 payment' and that adminContentBypass requires 'allowlisted key + X-AgentAEO-Admin-Content', but doesn't provide additional meaning beyond what's in the schema for auditId or packageType.

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 the tool's purpose: 'Start Content Suite generation (HTML + JSON-LD + llms.txt) for a completed audit.' It specifies the exact output format and the required input condition (completed audit), and distinguishes it from siblings by mentioning the async nature and the need to poll check_aeo_content_suite_status.

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 provides explicit guidance on when to use this tool vs alternatives: it mentions using adminContentBypass for admin QA without Cashfree, otherwise requiring orderId after payment. It also specifies the polling mechanism with check_aeo_content_suite_status and distinguishes from run_aeo_audit by focusing on content generation post-audit.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the operation is asynchronous ('async'), returns an auditId immediately, and has tier-based limitations (free tier stops at step 2). It also implies rate limits or polling intervals ('every 10–15s'). However, it doesn't detail error handling, timeouts, or authentication needs, leaving some gaps.

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 highly concise and well-structured: two sentences that front-load the core action and immediately follow with essential usage instructions. Every sentence earns its place by providing critical operational details without redundancy or fluff.

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?

Given the tool's complexity (async operation with polling) and lack of annotations or output schema, the description is largely complete. It covers the async nature, return value (auditId), polling requirements, and tier limitations. However, it doesn't explain what 'step 2' entails or potential errors, leaving minor gaps for an agent to handle edge cases.

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 100%, so the schema already documents all parameters (url, keyword, tier) with descriptions and defaults. The description adds no additional parameter semantics beyond what's in the schema, such as explaining keyword selection impact or tier implications in more depth. Thus, it meets the baseline but doesn't enhance understanding.

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 the tool's purpose: 'Start an AEO audit for a URL (async).' It specifies the action ('Start'), resource ('AEO audit'), and scope ('for a URL'), distinguishing it from sibling tools like check_aeo_audit_status or generate_aeo_content_suite by focusing on initiating an audit rather than checking status or generating content.

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 provides explicit usage guidance: it instructs to 'call check_aeo_audit_status every 10–15s until is_complete or free_preview_ready' and notes that 'free tier stops at step 2.' This gives clear when-to-use context (start audit, then poll) and distinguishes from alternatives by implying this is the entry point for audits, with check_aeo_audit_status as the follow-up.

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