searchatlas_otto_seo

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

No annotations are provided, so the description carries full burden. It mentions 'automation' and 'deploys' which implies execution/mutation, but doesn't disclose critical behavioral traits: whether this is a read-only preview or actually makes changes, what permissions are needed, whether it's destructive, rate limits, or what the output looks like. For a tool with 'deploys' in its description and no annotations, this is a significant gap in transparency.

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 extremely concise - a single sentence that efficiently communicates the core functionality. Every word earns its place: 'on-page SEO automation' establishes the domain, and the three-item list specifies the scope. No wasted words or redundant 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 an automation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'deploys' means operationally - whether this executes changes or just plans them, what the response contains, or how it differs from related tools. The 100% schema coverage helps with parameters, but the behavioral context is critically lacking for what appears to be a mutation/execution 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 description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain how 'message', 'project_id', 'playbook_id', or 'plan_mode' relate to the SEO automation process. With high schema coverage, the baseline 3 is appropriate as the description doesn't add value but doesn't need to compensate for schema gaps.

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 as 'on-page SEO automation' with specific actions: 'deploys technical fixes, schema markup, and content optimizations.' This provides a clear verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'searchatlas_content' or 'searchatlas_run_playbook' which might also handle content or automation aspects.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools like 'searchatlas_content', 'searchatlas_run_playbook', and 'searchatlas_website_studio' that might overlap in SEO or automation domains, there's no indication of when this specific automation tool is appropriate versus those others. No prerequisites, exclusions, or contextual boundaries are mentioned.

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