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

Discloses permission requirements and access restrictions beyond annotations. Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds value by warning about business tier limitations and required pre-checks.

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?

Description is front-loaded with the core purpose in the first sentence, followed by concise usage guidelines. No unnecessary words or repetition. Perfectly scoped for the information provided.

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 10 parameters, a nested object, no output schema, and 0% schema coverage, the description is insufficiently complete. It covers permissions and preconditions but omits parameter meanings, return values, and side effects, leaving the agent underinformed for correct invocation.

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%, meaning no parameter descriptions in the schema. The description only mentions 'optional discount configuration' without detailing any of the 10 parameters (e.g., communityId, upsellId, title, description). It does not compensate for the lack of schema descriptions.

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 states 'Update an upsell and optional discount configuration', clearly specifying the verb (update) and resource (upsell). It differentiates from sibling tools like create_upsell or delete_upsell by implication, but does not explicitly contrast with update_discount tools.

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?

Provides explicit prerequisites: check business permissions, call check_business_tool_access, show grace-period warning and resubscribe link, and never proceed when access is blocked. Also states FREE businesses cannot use this tool. However, it does not compare to alternative tools like create_upsell or delete_upsell.

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