Add keywords to an AutoSEO content plan

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

Beyond annotations, the description discloses detailed behavioral side effects: appends keyword text to config.topics, marks rows in_plan, and does not trigger publishing. It also adds safety context with CAPABILITY `draft` and the assurance that content cannot reach an audience on its own. This is valuable, non-redundant behavioral disclosure.

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 and front-loaded with the primary action, followed by essential side effects and safety info. Every sentence contributes meaningful information without redundancy or excessive length.

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 tool's moderate complexity, the description covers purpose, exact modifications, non-behaviors, approval gating, and capability classification. With all parameters documented in the schema and no output schema, the description provides sufficient context for an agent to invoke the tool correctly.

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 descriptions already cover all three parameters at 100%. The tool description adds high-level context about what happens to keyword rows but does not add specific parameter-level details beyond the schema, so a baseline score of 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 the tool's function: 'Add selected persisted keyword rows to an existing AutoSEO content plan.' It identifies the exact action, target resource, and distinguishes itself from tool siblings by explicitly noting it 'does not generate or publish an article.' This differentiates it from autoseo_generate_post and other publication 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?

The description provides context on when to use the tool by clarifying what it does not do ('does not generate or publish an article') and that later generation is gated by approval. However, it does not explicitly name alternative tools or specify exact conditions for use, stopping short of a full when/when-not/alternatives breakdown.

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