List dossiers

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

Annotations already mark readOnlyHint=true, so the safe read behavior is covered. The description adds the 'most recently updated first' ordering, which is a behavioral trait not present in structured fields. It does not contradict the annotations and provides useful sorting 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?

The entire description is six words and contains no filler or repeated schema information. It front-loads the only non-obvious behavior (ordering). It is perhaps terse but not wasteful.

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 read-only list with one optional parameter, the description plus schema and annotations are nearly sufficient. The description covers ordering, the schema covers the status filter, and annotations cover safety. It does not mention pagination or explicit 'all dossiers' scope, but the output schema and simplicity limit the gap.

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?

The single optional status parameter is fully documented in the schema with 'Filter by status; omit for all' and an enum of acceptable values. Since schema_description_coverage is 100%, the description does not need to add parameter detail. The tool description adds no additional parameter semantics, so baseline 3 applies.

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 'Dossiers most recently updated first' conveys the result ordering but does not explicitly state an action; the title 'List dossiers' supplies the verb and resource. It distinguishes the tool from get_dossier by plural scope, but not explicitly from listing/searching alternatives. This is clear but not maximally specified.

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?

There is no statement about when to use list_dossiers instead of get_dossier, search_companies, or create_dossier. The ordering information implies a read-only list use, but no exclusions or alternative routing are given.

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