products_seo_audit

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 reveals a significant restriction (requires a higher plan), which is useful, but it completely hides the tool's core behavior, side effects, or return value. This partial transparency is insufficient for a tool that cannot even be invoked without an upgrade.

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 short, but conciseness is not the issue—under-specification is. It spends its only sentence on an upgrade warning rather than explaining the tool's purpose. The content does not earn its place because it omits essential information that a concise description should include.

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 has no parameters, no output schema, and no annotations, the description is the only source of contextual information. It fails to explain the tool's purpose, behavior, or expected use, making it impossible for an agent to know what the tool does or when to invoke it. This is completely inadequate.

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 has zero parameters, so the description is not expected to explain parameter details. The baseline for 0 parameters is 4, and the description does not contradict or fail to compensate for anything since there are no params to document.

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 does not state what the tool does at all. It only mentions an upgrade requirement and points to 'license_status', leaving the actual function of 'products_seo_audit' entirely unspecified. The name suggests an SEO audit tool, but the description provides no verb, resource, or outcome.

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 only guidance is to use 'license_status' to see upgrade options, which is an alternative for handling licensing, not for the tool's intended use. There is no clear 'when to use this tool' context, no exclusions, and no mention of what scenarios warrant calling this tool versus siblings.

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