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

Annotations already declare write (readOnlyHint=false), destructiveHint=true, and idempotentHint=true. The description adds real behavioral context beyond that: preferences persist and are 'applied in later sessions', value=null deletes the key, value is capped at 500 chars. It doesn't describe the response body or what happens on partial/invalid input, keeping it out of 5 territory.

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 core is tight and front-loaded around the preferences semantics, but the closing fragment ('key tracked_search_terms + marketplaceId, searchTerms: value track') is garbled text that costs clarity without conveying a complete thought.

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?

For a 6-parameter write tool with no output schema and annotations covering the safety profile, the description covers the main mutation and deletion semantics adequately, but leaves the tracked_search_terms workflow (a key plus marketplaceId plus a terms array) unexplained and says nothing about success/failure behavior.

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 67%, so the schema already documents key, value, searchTerms, and marketplaceId; the description adds value over that only by clarifying that value=null removes the preference and by glossing categories ('targets (business goals)'). The final clause about tracked_search_terms, marketplaceId, and searchTerms is grammatically broken and fails to explain how those parameters combine, which is exactly the gap the schema leaves open.

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 opening sentence states a specific verb and resource ('saves business profile data') and the following clauses define the 'preferences' section as saving a standing rule applied in later sessions, so the agent can tell this is a write/persistence tool distinct from read siblings like get_entities or query. It stops short of naming any sibling or contrasting with submit_mutation, and the trailing fragment ('key tracked_search_terms + marketplaceId, searchTerms: value track') muddies rather than sharpens purpose.

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 phrase 'Saves a standing rule the user stated for this account' implies the trigger context (persisting user-stated preferences across sessions), which is useful implied usage. But there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as submit_mutation or describe for other profile operations.

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