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

Beyond the readOnly/idempotent annotations it discloses real behavior: no sign-in required, every answer carries a shareable setup link, unsupported systems should be answered with a prefilled request URL, and spreadsheet sources additionally return a template with download link, tabs and columns. The one weakness is that its enumerated 'supported today' list (22 systems) is far shorter than the schema enum (63), so an agent is told to declare enum-valid systems like airtable unsupported without any explanation of that gap.

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 routing and behavioral content is front-loaded and dense, but the flat enumeration of ~22 supported systems duplicates the schema enum and pushes the prose past a reasonable length, and its divergence from the enum makes the bulk actively confusing rather than merely redundant.

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 an output schema present, the description needn't document return values, and it covers invocation modes and the request-form fallback thoroughly. It leaves one unresolved case: what an agent should do when a value is valid per the enum but absent from the stated supported list.

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 would be 3, but the description adds genuine semantics the schema lacks: zero systems names both products, one system lists every partner plus what travels, two systems detail that specific pair, and a spreadsheet source triggers extra template output. Only the system-key vocabulary is restated rather than clarified.

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?

Opens with a concrete resource (integrations between two systems) and states exactly what the tool answers: what CRM Connector supports, which systems pair with which, and what travels (record types, direction, trigger events, ready rules). It is clearly separable from siblings like plan_integration or get_field_details, and the name is not merely restated.

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: "Not for setting up an integration with chosen record types (use plan_integration), for which fields travel (use get_field_details), for how to connect a system (use get_connection_guide), for a person's own integrations or sync results." It also gives a fallback script for unsupported systems, which is unambiguous when-to-use guidance.

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