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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine scope context — only metadata/approved fields are returned, with no secrets, contacts, or original files — which is useful for deciding whether this tool can answer a question. It says nothing about pagination, result caps, or authorization failure behavior despite limit/offset params.

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 short clauses, front-loaded with the action and immediately followed by the important scope restriction. No filler, though the 'through the existing application' phrase adds little.

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 4-parameter listing tool with no output schema and zero schema descriptions, the definition leaves the agent without search semantics, pagination guidance, or return shape. The content-scope note is valuable but insufficient to call this correctly with confidence.

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 four parameters, so the description must compensate and does not. It never explains what targetId identifies, what 'query' searches over (filename, metadata, owner?), or how limit/offset should be used.

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 location documents') and constrains the returned fields to metadata/approved data. It does not differentiate from nearby siblings such as list_document_library, list_employee_documents, or list_document_portal_user_metadata, so an agent still has to guess which document-listing tool fits.

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 of when to use this versus the other document/credential listing tools, and no prerequisites or exclusions beyond the content filter. 'Through the existing application' hints at a proxying pattern but gives no actionable condition for selection.

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