seo_brand_vs_nonbrand

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions using a regex but does not disclose potential side effects, error handling (e.g., invalid regex), authentication requirements, or the nature of the output. This is insufficient for a tool that processes data.

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 a single, concise sentence that efficiently communicates the core purpose. It is front-loaded and avoids redundancy. However, it could be slightly expanded to include usage context without losing conciseness.

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 four parameters, no output schema, and several sibling tools, the description lacks completeness. It does not explain what 'performance split' entails, what the output format is, or how results are organized. Users would need additional documentation to use the tool effectively.

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%, meeting the baseline for this dimension. The description adds no extra meaning beyond the parameter descriptions; it merely reiterates the use of a regex, which is already detailed in the 'brandRegex' parameter. No additional semantic value is 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 the tool analyzes performance split between Brand and Non-Brand queries using a regex. It specifies the action, resource, and method, making the purpose clear. However, it does not explicitly differentiate from similar sibling tools like 'brand_analysis', so not a 5.

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 no guidance on when to use this tool versus alternatives such as 'brand_analysis' or 'seo_primitive_is_brand'. There is no mention of prerequisites, limitations, or exclusions, leaving the agent without decision context.

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