Bulk-import rows into a Rootr CRM

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

Annotations indicate non-readOnly and non-destructive. The description adds that it is a bulk import operation and auto-links into the knowledge graph. However, it does not disclose details like whether duplicates are handled, error behavior on partial failures, or any required permissions beyond the CRM 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?

Two sentences efficiently convey purpose, usage context, and parameter hints. No unnecessary words, well-structured for quick understanding.

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 core functionality, parameter semantics, and a key behavioral point (auto-linking). It lacks details on return values (e.g., count of imported rows, error handling), which are important for a bulk import tool. Given no output schema, more information on expected response would be beneficial.

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 coverage is 100% with descriptions for all parameters. The description adds value by explaining that the 'rows' array must match the create shape of the chosen entity (referencing rootr_crm_upsert_* tools), and clarifies the 'entity' parameter options. This goes beyond the schema alone.

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 the tool bulk-imports rows into a Rootr CRM as companies, contacts, or deals in one call, using the 'entity' parameter. It distinguishes from sibling upsert tools by explicitly mentioning it's an alternative to calling those one row at a time.

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 tells when to use this tool: for migrating a spreadsheet/CSV of leads or accounts instead of using upsert tools individually. It mentions the entity parameter and refers to the create shapes of sibling tools for row format, providing actionable guidance. It does not explicitly list when not to use, but the context is sufficient.

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