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

Annotations only say readOnlyHint=false and destructiveHint=false; the description goes well beyond that by disclosing server-side fetching, staging inside the client's tenant for certification, resolution of the PBC open item, and the deliberately narrow return surface (column names plus where to certify the mapping). It also makes an important safety guarantee explicit: no rows of client data pass through the model.

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?

Front-loaded with the right idea, but the by-reference point is restated three times ('BY REFERENCE', 'never the file's contents', 'doesn't touch the model', 'no LLM on the money path') and the closing tagline is rhetorical rather than informative. Roughly a third of the text could be cut without losing guidance.

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 usefully says what comes back (column names and the certification location), which is exactly what an agent needs to continue the workflow. It omits failure modes (expired link, unreachable URL, wrong tenant) and whether the call is idempotent for a given open item.

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 real meaning: it explains that signed_url and upload_handle are mutually alternative delivery mechanisms and that contents are never pasted in, which reinforces the 'by reference' contract in the schema. It still does not clarify required-vs-optional selection between the two transport params.

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 ('receive a client document into an engagement') and immediately pins down the mechanism ('BY REFERENCE — a signed https link or upload handle, never the file's contents'). That mechanism is what separates it from siblings like ingest or request_documents, so an agent can route correctly without opening the schema.

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?

Usage is implied: it is the path for getting client data in, and it 'resolves the matching PBC open item', which hints at the post-request step. However, it never names an alternative (request_documents, ingest) or states an explicit when-not-to-use condition, so the agent must infer the ordering from sibling names.

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