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

Annotations already declare idempotentHint and destructiveHint, but the description adds meaningful behavior: PATCH/POST mechanism, duplicate handling ('duplicates are updated, not re-created'), and re-run safety. It does not fully describe response/error behavior, but it enriches the annotation profile without contradicting it.

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 compact and front-loaded, starting with the core verb and purpose. The sentences each carry distinct value: operation semantics, idempotency/re-run safety, usage boundary with alternative, and invocation guidance. No words are wasted.

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 5-parameter tool with no output schema, the description covers purpose, operation behavior, scale guidance, and the alternative tool. It omits return/response format and error-prevention details beyond the key-fields warning, so it is nearly complete but slightly short of fully self-sufficient.

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%, so the baseline is 3. The description adds value by explaining how to supply rows ('JSON array of objects') and by warning the agent to resolve key fields from the knowledge base rather than guessing, which goes beyond the schema's basic field descriptions.

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 states a specific verb and resource: 'Idempotent import of rows into any entity via OData'. It further clarifies the exact operation semantics (PATCH when the record exists, otherwise POST), which unambiguously distinguishes it from read/export tools like odata_export_entity.

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 explicitly states when the tool is appropriate: 'small-to-medium transactional loads' and gives a size example. It also names the bulk-load alternative, dmf_import_file, and tells the agent to resolve key fields from get_data_entity_info rather than guessing them.

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