seo_primitive_ranking_bucket

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

No annotations exist, so the description must fully disclose behavior. It only states the basic function without detailing side effects, data requirements, or output format. For example, it doesn't mention whether this is a read-only operation or any prerequisites.

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 short sentence with an example, making it concise and easy to scan. However, it could be longer to cover missing 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?

For a tool with no output schema and no annotations, the description is insufficient. It lacks usage context, behavioral details, and parameter clarification, leaving the agent to guess important aspects.

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 description does not add meaning beyond the schema. The schema already documents 'position' and 'engine' with minimal descriptions. The example 'e.g. Top 3, Page 1' refers to the result, not the parameters. The 'engine' parameter description in the schema is just a restatement.

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 retrieves a ranking bucket for a position, with examples like Top 3 and Page 1. It uses a specific verb (Get) and resource (ranking bucket). However, it does not explicitly distinguish from sibling primitive tools like seo_primitive_is_brand.

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 alternatives (e.g., other primitive tools or SEO analytics tools). There are no when-not or alternative recommendations.

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