blog_add_seo

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that the tool generates blog SEO optimization and is a Pro feature; it does not disclose whether files are modified, what permissions are needed, whether the operation is reversible, what the output looks like, or what 'Pro feature' means operationally for the caller.

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 short and front-loaded, with no filler words. The 'Pro feature' note is arguably useful context even if underdeveloped. It earns its place as concise, though brevity comes at the cost of substance.

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?

With no annotations, no output schema, and a sparse description, an agent lacks essential context for correct invocation and expectation-setting. The tool could modify a blog project, generate a report, or produce configuration, but nothing in the description clarifies this, making the definition incomplete for a tool with two parameters and no documented output.

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 documents only 'directory' with 'Project directory', while 'api_key' has no description. The tool description adds no parameter-level meaning, so an agent is left to infer that api_key is required for Pro access and what exactly the directory should contain. At 50% schema coverage, the description should compensate, but it does not.

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 states a verb ('Generate') and a resource ('blog SEO optimization'), but it does not specify what artifact or outcome is produced—suggestions, code, meta tags, configuration, or a report. It is distinguishable from blog_generate_setup and blog_add_rss only by the 'SEO' keyword, but remains vague compared to more specific sibling names like seo_audit_meta or seo_generate_fixes.

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 about when to use this tool versus alternatives such as seo_generate_fixes, seo_audit_meta, or blog_add_rss. The phrase 'Pro feature' hints at a prerequisite but does not explain when this tool should be selected over related sibling tools.

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