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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered; the description still adds real value by stating the downstream effect ('Future discovered prospects will no longer sync'). It does not say whether credentials are deleted or whether already-synced prospects are affected.

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 short sentences, front-loaded with the action, followed by consequence and safety note; nothing is padded. The idempotency sentence partially duplicates idempotentHint, but it is cheap and reads naturally.

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, return values need no explanation, and the zero-parameter schema needs no further documentation. The description covers effect and idempotency; the only gap is scope of destruction, i.e., whether credentials or existing synced data are removed.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the schema cannot already convey. The description correctly adds no per-parameter text.

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 ('Disconnect your Odoo CRM'), which is plainly distinguishable from siblings like set_odoo_credentials and get_crm_connection. It does not explicitly name an alternative, but the resource is unique among siblings so mis-selection is unlikely.

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?

Usage is implied by the single-purpose name and the stated effect, but there is no explicit when-to-call guidance and no routing to siblings such as get_crm_connection for checking current connection status first. Adequate for an obvious single-action tool, but leaves inference to the agent.

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