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

Goes far beyond the destructive/openWorld annotations: discloses the 30-requests-per-day cap, that writes with the help centers' keys are refused during migration while reads still work, that the 7-day deletion clock is paused, that PII (the email) is sent to a third party, and that nothing is emailed automatically. It also explains the external_id in-place replacement behavior, which is a subtle and important side effect.

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?

Dense but well-organized: purpose, when-to-use, per-source mechanics, side effects, consent requirement, return fields, rate limit. It is long, but nearly every sentence carries operational information; a small amount of tightening in the returns paragraph would help.

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 no output schema, the description fully enumerates the return fields (request_id, status_token, handoff_url, help_centers, expected_by) and even instructs how to use and conceal the token. Consent, rate limits, and downstream side effects are all covered, so an agent can call this correctly without guessing.

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, but the description adds cross-parameter meaning the schema cannot: each source becomes one help center, and putting an api_key in a source's agent_key fills an existing help center rather than creating a new one. The external_id/existing-article guidance is extra context not present in the schema.

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 up front ('File a migration request: HelpCenter.io moves one or more knowledge bases (up to 50) into HelpCenter.io') including the scope cap and turnaround. This is clearly distinguishable from sibling tools like helpcenter_run_import or helpcenter_create_help_center.

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 four explicit trigger conditions (KB too big, create_help_center returns limit_reached/capacity_reached, scan_import cannot read the source, multiple KBs) and names the alternative tools being superseded. It also explains the fallback path (known platforms auto-migrate, anything else goes to the migration team).

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