ingest_batch_api_poll

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

With no annotations, the description carries the behavioral burden. It discloses meaningful behaviors: PII redaction and mapping unique stitched identities. However, it omits important details such as idempotency, potential side effects, storage overwrite behavior, or failure handling. The claim 'instantly' is vague but adds some context.

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 description is composed of two concise sentences with no filler. It is front-loaded with the primary purpose, followed by secondary processing details. Every sentence adds value, though the second sentence could be more specific about what 'maps unique stitched identities' means.

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 tool with four required parameters, no annotations, and an output schema, the description is incomplete. It does not explain how parameters relate to the ingestion process, what the output contains, or any failure/retry behavior. The presence of an output schema reduces the need to describe return values, but the absence of parameter semantics and usage guidance makes the tool hard to invoke 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?

The input schema has four required parameters (crm_lead_id, email_address, payload_json, source_platform) with 0% description coverage. The tool description does not mention any of these parameters, their purpose, or expected format. This is a critical gap since the schema alone only lists names and types without additional meaning.

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 clearly states it 'Ingests heavy, non-real-time data (CRM profiles) directly to on-disk Cold Storage.' The verb 'ingests' and resource 'Cold Storage' are specific, and the phrase 'non-real-time' distinguishes it from the sibling tool 'ingest_realtime_webhook'. However, the name includes 'api_poll' but the description does not mention polling, which is a minor gap.

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?

The description implies usage for batch, non-real-time data, which contrasts with the realtime sibling tool, but it does not explicitly state when to use this tool vs alternatives or include any exclusions. There is no mention of prerequisites or conditions, leaving the application context partially inferred.

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