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

Annotations already indicate the tool is neither read-only nor destructive. The description adds valuable behavioral context: 'nextjs' is credential-free and returns a blog API key, and the operation requires an agent API key. It explains side effects like returning credentials, which goes beyond the annotations. No contradiction detected.

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: two sentences that front-load the purpose and then provide specific, actionable configuration details. There is zero wasted text, and every clause adds meaningful information. This is exemplary conciseness.

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?

The description covers the two primary integration options (nextjs and webhook) and auth requirements, but it does not mention the other valid publishIntegration values (wordpress, ghost, shopify, rest, none) from the schema. With no output schema, return values are only specified for nextjs. This is adequate for a simple configuration tool but has clear gaps for users considering other integrations.

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 description coverage is 0%, so the description must add meaning. It explains the semantics of publishIntegration ('nextjs' vs 'webhook'), conditional usage of publishWebhookUrl, and the meaning of publishMode. However, it omits details for publishWebhookSecret and the additional integration enum values (wordpress, ghost, etc.), leaving some parameters partially unexplained. Still, the description meaningfully clarifies the most important 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?

The description clearly states the tool's function: 'Configure where a site publishes.' This is a specific verb+resource pair that immediately distinguishes it from siblings like publish_article (publishing articles) and create_site (site creation). It also enumerates the main configuration options, making the purpose unambiguous.

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 clear context for when to use the tool: to configure a site's publishing destination. It gives concrete instructions on how to set different integration types (nextjs vs webhook) and publishMode, but does not explicitly mention alternatives or when not to use it. This is clear context without exclusions, warranting a 4.

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