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

Adds meaningful behavioral context beyond the annotations by saying the tool does not navigate and that public pages are read by the agent before `import_prospects`. However, with `readOnlyHint=false`, it does not clarify what mutation or side effect "preparing" entails, nor what the tool returns.

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?

Two dense, front-loaded sentences with no filler. The purpose, scope, and handoff are stated immediately, and the platform list is compact.

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?

The description covers the planning workflow and next tool well for a low-complexity tool, but it omits the meaning of the required `id` and does not describe the mutation implied by `readOnlyHint=false`. Those gaps matter for correct invocation.

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 input schema has a single required `id` with 0% schema description coverage, and the description never explains what that `id` identifies. Naming the `prospect_searches` resource gives a weak hint, but the parameter remains effectively undocumented.

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 the specific action ("Préparer une recherche de prospects") plus the resource (`prospect_searches`), enumerates what the plan contains, and explicitly says what the tool does not do ("Outil ne navigue pas"). It also distinguishes the next step, `import_prospects`, so the agent can tell it apart from the import tool.

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 a clear workflow: this tool only prepares the search plan, then the agent reads public pages and calls `import_prospects`. That is useful when-to-use context, though it does not spell out explicit exclusions or prerequisites beyond non-navigation.

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