list_contracts

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

readOnlyHint=true already establishes this is a safe read, so the bar is lower. The description adds organizational scope but says nothing about pagination behavior; 'List all' is mildly in tension with the schema's default limit of 20, though not a true contradiction.

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 short sentences, front-loaded with the core purpose before the filtering capability. No filler or redundancy, though the filtering clause is a partial list that stops short of full coverage.

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 simple, fully documented read-only list tool this is minimally adequate, but with no output schema it says nothing about the shape of returned contract records or pagination semantics, which an agent calling a paginated list endpoint would benefit from knowing.

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% with documented enums for type and status, so the schema carries parameter meaning. The description only echoes three of the six filters and omits country, worker_id, limit, and offset, adding no new semantic detail.

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?

States a specific verb and resource ('List all contracts') and scopes it to 'your Deel organization'. It does not explicitly differentiate itself from siblings like get_contract or list_workers, but the enumeration/collection intent is unambiguous.

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 (browse/filter the contract collection) and names filterable attributes, but gives no explicit when-to-use guidance, no mention of when to prefer get_contract for a single record, and no prerequisites.

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