seopass_lighthouse_plan

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

The description discloses that execution and persistence are separate, implying this tool is read-only or non-mutating. However, with no annotations, the burden is on the description to fully disclose side effects, auth needs, or rate limits, which are absent.

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 two-sentence description is concise and front-loaded with the verb 'Build'. Every sentence adds value, with no redundant or extraneous information.

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 3 parameters, no output schema, and no annotations, the description is incomplete. It does not describe the return value (e.g., plan ID, status), leaving the agent uncertain about what to expect after invocation.

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% with all parameters described. The description adds no extra parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 it builds a Lighthouse execution plan for a SEOPass target URL, with the phrase 'Execution and persistence land in a later chunk' implying it is a preparatory step. While it distinguishes from siblings like seopass_run and seopass_status by focusing on planning, it does not explicitly differentiate from other seopass tools.

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 or prerequisites. The description does not indicate whether this tool should be called before seopass_run or under what conditions it is appropriate.

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