One request

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

Describes synchronous behavior, immediate result return, and structure of raw_results and options parameters. No annotations provided, so description carries burden; adequately covers key behavioral traits.

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?

Three concise sentences: purpose, usage guidance, and parameter clarification. No fluff, front-loaded, each sentence adds value.

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?

Sufficient for a synchronous parse tool with clear use case. Covers result format and overrides, but lacks error handling or prerequisite details. Differentiates from siblings well.

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?

Adds meaningful detail beyond input schema, especially for raw_results (explicit difference between array and string) and options (specifies the object structure). Schema already covers all params but description clarifies 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?

Clearly states the tool runs a single parse synchronously and returns results immediately. Distinguishes from sibling add_task by specifying it's for one-off lookups like suggest queries, SERPs, or pages.

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?

Explicitly advises when to use this tool (one-off lookups) and when not (many queries or saved output files), directing to add_task as alternative.

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