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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description goes beyond them by disclosing the result-cap behavior (default 500, lists can hold thousands, raise limit or call again), which tells the agent how to obtain a complete set. It does not describe rate limits or error behavior.

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 tight sentences, front-loaded with the core purpose, then the prerequisite, then the limit guidance. No filler; every sentence carries actionable information.

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, so return-value explanation is unnecessary, and annotations cover the safety profile. The description supplies the missing pieces: entity scope, prerequisite source for the ID, and pagination-style limit 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 description coverage is 0%, so the description must carry the load. It explains limit well (default 500, caps returned rows, large lists hold thousands, raise or re-call) and gives the origin of shared_set_id. customer_id, however, is left entirely undefined, so compensation is strong but not complete.

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?

States a specific verb (reads) and resource (the actual negative keywords inside a shared negative keyword list/shared set), and the parenthetical '(shared set)' pins the entity. It is clearly distinguishable from the sibling list_shared_negative_lists, which returns the lists themselves rather than their contents.

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?

Explicitly routes the agent to the prerequisite tool: 'Get the shared_set_id from list_shared_negative_lists.' That is a concrete when/how-to-obtain-input instruction. It does not, however, state when to prefer this over other negative-keyword readers such as list_microsoft_negative_keywords or list_negative_keywords.

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