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

Goes well beyond the annotations: the replace-not-merge semantics ('any facet key you omit is cleared'), the guarantee that body/title are untouched, the echoed return fields, 400-on-invalid-value behavior, required ESG_HUB_WRITE_TOKEN, and rate limiting. This is exactly the mutation-behavior context annotations cannot carry.

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?

Front-loaded with the replace action and clearing semantics, and every sentence carries information. It is dense and slightly run-on, but nothing is filler.

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?

An output schema exists, yet the description still frames the response briefly; combined with write-token, rate-limit, validation, and clearing behavior, an agent has everything needed to call it 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 coverage is 100%, so types are already documented, but the description adds real semantics: which facets are multi-value arrays vs the single-string content_type, that values are validated against the get_esg_metadata/list_industries vocabulary, and that page_id accepts permalink/slug/record ID with server-side resolution.

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?

Opens with a specific verb+resource+scope ('Replace the facet tags on one existing ESG Hub page') and enumerates the exact facet keys affected. An agent can immediately distinguish this from get_esg_page and flag_content.

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?

Explicit routing: 'Use it to curate tags; to read a page use get_esg_page, and to queue a removal use flag_content.' It names both the read and removal alternatives and the condition selecting each.

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