Update Blog

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

Annotations indicate mutability but not destructiveness; description only says 'update' without explaining whether it merges or replaces metadata, or any side effects. No additional behavioral context beyond the verb.

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?

One short sentence, no fluff. But it lacks substance; could include more context without being verbose. Adequate but not optimal.

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?

Missing key details: effect of update (partial vs full), no expected return value, no mention of required identifiers (website_id and blog_id) or constraints. Incomplete for an agent to use correctly without assumptions.

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 has 100% description coverage, so baseline is 3. Description adds no value beyond the schema; does not clarify semantics of nested 'seo' object or relationship between parameters.

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?

Description clearly states the action (update) and resource (blog post metadata), distinguishing it from sibling 'update_blog_content' which updates the body. However, it does not explicitly list the metadata fields (name, path, seo) which are in the schema.

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 on when to use this tool versus alternatives like 'update_blog_content', 'create_blog', or other update tools. Does not mention prerequisites or context.

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