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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/safety profile is known. The description adds genuinely new behavioral facts: the record is team-wide visible, it is not deduplicated, and no message is dispatched to the prospect. It does not say what the response contains (e.g., the new prospect ID), which is the remaining 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?

Three short sentences, front-loaded with the action and followed by the two most decision-relevant caveats (no dedup, no notification) plus the endpoint. No filler.

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 non-idempotent, open-world create with no output schema, the description covers visibility, dedup behavior and side effects. It leaves open what is returned and whether the prospect must be unique by email, but the essentials for a correct call are present.

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 description coverage is 100% with clear per-field descriptions, so the schema already carries parameter meaning. The description adds nothing field-specific beyond the implied 'name' requirement and the is_public/team-visibility hint, so the baseline 3 applies.

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 ('Create a sales prospect (lead) in Bind ERP') and implicitly distinguishes the record type from the sibling create_client/create_order tools. An agent can tell exactly what object is being created.

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 through binderp_list_prospects first, which is a concrete pre-call check. It stops short of naming when to use binderp_create_client instead (e.g., a company that is already a customer), so the alternative pathway is only implied.

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