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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive operation, so the description's main contribution is the 500-contact cap and the notion of a 'named batch'. It omits important behavior for a non-idempotent submit: whether resubmitting duplicates work, whether analysis is async, and how the resulting batch is identified for later retrieval.

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 single sentence is front-loaded and free of filler, but it is under-specified rather than genuinely concise for a batch-submission tool with three parameters. Brevity here costs the agent information rather than saving it effort.

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?

There is no output schema and no annotation clarifying return shape, yet the description never indicates what the agent gets back (a batch id or handle) or how to follow up. For a non-idempotent, open-world submission tool with a fully undocumented parameter set, this leaves the agent without enough to call it correctly.

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 0%, so the description must carry all parameter meaning. It covers 'contacts' (with a 500-item cap) and loosely implies 'name' via 'named batch', but says nothing about icp_profile_id — including what happens when it is left null, which is a defaulted optional parameter whose behavior is entirely undefined.

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?

The description gives a specific verb ('Submit') and resource ('contacts') and qualifies the operation as 'batch business-fit analysis', which implicitly separates it from the singular sibling analyze_contact. It stops short of naming the sibling or clarifying how the batch relates to get_batch/list_batches.

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?

There is no explicit when-to-use guidance: nothing says to prefer this over analyze_contact for single contacts, nor what to do after submitting (poll get_batch/get_analysis). The word 'batch' plus the 500 cap only weakly implies the usage context.

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