audit_conversion_flow

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 only states the tool 'audits friction' without explaining what it does internally, whether it is read-only, what data it inspects, what it returns, or any side effects. This is a significant gap, especially since there is no output schema.

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 brief, which is superficially concise, but under-specification is not true conciseness. A single vague sentence does not adequately serve the agent; it could be expanded with meaningful details while still remaining concise.

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 exists within a large ecosystem of audit and analysis tools, but the description gives no context about its role, inputs, outputs, or integration with other tools. There is no output schema, no annotations, and no elaboration on what 'friction' means, making the description insufficient for effective invocation.

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 input schema includes two parameters (taskId, pathname) with zero description coverage. The description does not explain the meaning or intended use of either parameter, the relationship between them, or how pathname's default '/' factors into the audit. Without any compensatory information, the agent cannot reason about parameter usage.

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 identifies a specific verb ('audit') and resource ('conversion flow'), but the phrase 'conversion flow friction' is vague and does not specify what aspects of the flow are examined or what constitutes friction. It is distinguishable from sibling audit tools like audit_page_seo or audit_metadata, though it could overlap with conversion-related analysis tools.

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?

No guidance is provided on when to use this tool versus the many sibling tools (e.g., analyze_cta_hierarchy, analyze_product_discovery, generate_conversion_plan). It does not state prerequisites, typical scenarios, or exclusions, leaving the agent without context for proper selection.

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