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

With no annotations provided, the description must fully disclose behavior. It states 'Queue a rank tracking check', implying asynchronous operation, but does not explain what 'queue' entails, whether the check is destructive, or any rate limits or auth requirements.

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 with no redundant information. Every word is necessary and directly to the point.

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 (queuing an async task) and the absence of an output schema, the description is incomplete. It does not explain how to check the job status (e.g., via agentseo_job_status), what the response looks like, or any limitations.

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 50% (only 'keyword' and 'url' have descriptions, while 'sync' and 'location' lack descriptions). The tool description does not add any parameter details beyond the schema, failing to compensate for the missing descriptions of 'sync' and 'location'.

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 'Queue a rank tracking check for a URL and keyword' clearly states the action (queue) and the resource (rank tracking check), with specific parameters (URL and keyword). It distinguishes from sibling tools like agentseo_analyze_serp or agentseo_search, which have different purposes.

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 on when to use this tool versus alternatives. It does not mention any prerequisites, such as requiring an existing domain or campaign, nor does it indicate when not to use it (e.g., for instant results).

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