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

Beyond the readOnly/destructive annotations, it discloses the 10 MB cap, that the file is not stored, that a call costs 100 tokens, and what the response contains (brief, requirements with verbatim quotes, quotes_checked). Those are exactly the operational facts an agent needs before uploading a file.

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?

Dense but front-loaded: what it reads, how it is passed, the limits, then the return shape and next step. The opening clause is slightly convoluted in phrasing, and the format list could be compressed, but nothing is superfluous.

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, the description carries the return contract itself and does so (brief, requirements with quotes, quotes_checked), plus size limit, storage behavior, cost and follow-up step. Nothing material is missing for a 3-parameter upload-and-extract tool.

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%, so the baseline is 3, but the description adds that filename is 'best' provided (an encouraged optional) and that media_type should accompany the base64 payload. It still defers concrete media-type values to the schema's own examples rather than repeating them.

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 ('The premises requirements a file states') and enumerates the accepted file kinds, so an agent can tell it apart from claro_search_premises or claro_get_premises without opening a schema. The closing 'nothing is searched here' pins the scope further.

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?

Gives an explicit workflow: show the brief to the user, then pass it to claro_search_premises, which names the natural next tool and excludes search from this one. It does not cover the case where requirements already exist as text rather than a file, so there is no stated alternative for that path.

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