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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds two pieces of behavior beyond that: Google and G2 sources begin an ongoing review sync (a lasting side effect, not just a one-time write), and the feature requires a paid plan. It does not say what the call returns or whether re-adding an existing source errors.

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 core action, then broken into compact per-type clauses with no filler. The telegraphic style ('type google: name and place_id from find_google_business') is dense but readable; a slightly more structured list form would read better, but nothing is wasted.

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 create tool with no output schema, the definition covers the important agent-facing facts: how to configure each type, the cross-tool dependency for place_id, the sync side effect, and the plan requirement. The remaining gap is what is returned (presumably the new source id) and whether duplicates are rejected.

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 the baseline is 3, and most of the description's parameter text restates the schema descriptions almost verbatim. The one genuine addition is the conditional dependency the schema cannot express — which parameters are required per type — plus the origin of place_id from find_google_business.

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 and resource ('Adds a review source') and immediately breaks the operation into its three concrete variants (google, g2, manual), which lets an agent distinguish it from add_review, import_reviews, and update_review_source without opening a schema.

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?

Gives per-type guidance and explicit hand-offs: manual sources get their reviews via add_review or import_reviews, and the google place_id comes from find_google_business. It also surfaces a prerequisite ('Paid plans'). It stops short of stating when not to use this tool (e.g. re-using an existing source via list_review_sources/get_review_source).

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