update_site_metadata

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

Transparently describes the partial update behavior and that it returns the updated fields. With no annotations, it adequately covers the nondestructive nature. Could mention if changes are reversible.

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?

Three concise sentences, front-loaded with purpose, no redundancy. Every sentence adds value.

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 10 optional parameters, no annotations, and an output schema, the description covers purpose, partial update, and return value. Could mention authentication or rate limits, but not essential for this 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 coverage is 0%, so description compensates by grouping parameters into categories (title/description, meta, OG, Twitter). However, individual parameter constraints or formats are not defined, which is acceptable given the schema's simplicity (all strings).

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 tool updates the blog's identity and SEO/social metadata, listing specific field groups (title, meta, OG, Twitter). However, it does not explicitly differentiate from sibling tools like update_branding.

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?

States that only provided arguments are changed (partial update). No explicit guidance on when to use this tool vs. alternatives, nor any prerequisites or limitations.

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