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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'retrieves data without changing records' largely repeats structured data. The 'without spending credits' claim is genuinely additive cost context, and the prospect-count note hints at payload shape, but pagination behavior and the mode/driver/date filtering semantics go undisclosed.

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?

Four short sentences with the core purpose front-loaded. 'List drives. List recorded drives for the workspace.' is mildly redundant, but nothing is bloated.

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?

With no output schema, no annotations covering payload shape, and a nested parameter object at 0% description coverage, the description should explain the mode filter, pagination and date/driver filters. It instead stops at the resource name and a one-line return hint.

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 0% and the single parameter is a nested query object with six undocumented sub-fields (mode enum, page, per_page, started_after, started_before, driver_user_id). The description mentions none of them, so an agent gets no meaning beyond bare property names.

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 recorded drives for the workspace') and notes what each item reports. It does not explicitly distinguish itself from the sibling dealmachine_get_driving_drives_id, but the plural/workspace scope makes the difference inferable.

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?

No statement of when to use this versus dealmachine_get_driving_drives_id for a single drive, and no guidance on filtering or prerequisites. Only the implicit 'for the workspace' scope hints at usage.

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