seopass_run

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

No annotations are provided, so the description carries the full burden. It states that the tool does not persist results and returns a plan (crawl and Lighthouse execution plan). This discloses key behavior, but lacks details on side effects, permissions, or rate limits. The description is adequate but not comprehensive.

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 concise with two sentences: the first states purpose, the second adds behavioral detail. It is front-loaded and every sentence adds value. No wasted words.

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 lack of output schema, the description provides adequate context: it returns a plan. It mentions 'Chunk 1' which implies a multi-step process but does not explain further. The description helps differentiate from other Pass tools by specifying SEOPass and crawl/Lighthouse. It is mostly complete for a planning tool.

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 coverage is 100%, so the baseline is 3. The description does not add new meaning beyond what the schema already provides for 'url' and 'pack_name'. It effectively ties parameters to the planning context but adds no additional detail.

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's purpose: 'Plan a SEOPass run against a URL or registered pack.' It specifies the verb 'plan' and the resource 'SEOPass run', and distinguishes from siblings like seopass_status or seopass_register_pack by focusing on planning without persisting results.

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 implies when to use this tool: for planning a run and previewing results without persistence. It mentions 'Chunk 1' which suggests a workflow, but does not explicitly state when not to use it or name alternatives. However, the context is clear enough for an AI to infer usage.

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