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

Annotations already declare a safe, idempotent, closed-world read, so the description's remaining job is narrower — and it does add real value beyond them by disclosing what is excluded from results (no secrets, contacts, or original files) and that only metadata/approved fields surface. It stops short of noting pagination behaviour or how "authorised" is enforced per caller.

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 compact sentences with the read scope front-loaded and no filler. It is efficient but leans toward under-specification rather than earning its brevity, since the saved words are exactly the parameter guidance an agent needs.

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 parameter descriptions, and no annotation covering permissions, the definition should say more: which documents are returned, what targetId identifies, and how paging works. The field-exclusion note helps, but an agent could not confidently construct a valid call from this description alone.

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% across all four parameters, so the description must compensate and largely does not. Only the word "employee" weakly implies that the required targetId is an employee identifier; query, limit, and offset are never mentioned, nor are the max-100 limit and offset ceiling that shape paging strategy.

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 ("read authorised employee documents") and scopes the content to metadata/approved fields. However, it does not distinguish itself from near-siblings such as list_document_library, list_location_documents, or list_document_portal_user_metadata, so an agent cannot route unambiguously without inspecting schemas.

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 tool versus the several other document-listing siblings. "Through the existing application" and "authorised" hint at a permission model but never describe when this listing is the right call or when it will return nothing.

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