Restore multiple Twenty CRM records

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

Annotations already cover safety: not read-only, not destructive, idempotent, open world. The description adds no extra behavioral context beyond 'restore soft-deleted records'. No contradictions.

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?

Single sentence with no wasted words. It is front-loaded and efficient, though the extreme brevity slightly detracts from completeness.

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 batch operation with 4 parameters and no output schema, the description lacks return value info, error behavior, or side effects. The filter mechanism and depth parameter are schema-documented but the description does not tie them together.

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 4 parameters. The tool description adds no parameter-level meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 verb 'Restore', the resource 'soft-deleted records', and the mechanism 'matching a required filter'. It distinguishes from siblings like the singular 'restore_record' and the opposite 'batch_soft_delete_records'.

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 restoring soft-deleted records with a filter but provides no explicit guidance on when to use this batch variant over the singular 'restore_record' or other siblings. No when-not-to-use or alternative context.

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