content_seo_research

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

The annotation already indicates destructiveHint=true and readOnlyHint=false, so the description does not need to repeat those. However, the description adds no additional behavioural transparency, such as side effects on data, resource consumption, or potential irreversible actions. It only says 'run' without elaborating on consequences.

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, consisting of two sentences and a two-line Args section. It avoids unnecessary verbosity and directly states the purpose and parameters. No filler or redundant content is present.

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 simplicity of the tool (two optional parameters, an output schema exists), the description provides sufficient context to understand its role as a dispatch action. It does not need to explain return values since an output schema is present. However, it could benefit from a brief mention of typical use cases or what the SEO research action might produce, but the current level is complete enough for a basic understanding.

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?

The schema has no descriptions, so the description compensates by stating 'message' is free-text objective and 'inputs' is optional JSON string. This gives a basic meaning, but it does not explain expected structure of inputs or examples, leaving the parameters only minimally understood. Since schema coverage is low, the description adds some value but not enough for full clarity.

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 runs a specific content domain agent action named 'seo_research', and mentions it routes through a dispatcher. This is more specific than a generic action name, but it does not elaborate on what SEO research entails or differentiate it from other content-related actions, so it is clear but not maximally distinguishing.

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, no prerequisites, and no conditions. It only states the mechanism of routing, which is not usage direction. This leaves the agent without explicit decision support.

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