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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds genuine value beyond that by bounding the data scope: 'Metadata/approved fields only; no secrets, contacts or original files,' which tells the agent what will not come back. It omits pagination behavior, keeping it from a 5.

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 tight clauses with zero padding, and the action is front-loaded. Efficient, though it is arguably too terse given the documentation gaps elsewhere.

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?

No output schema, no parameter documentation, and no selection guidance against ~90 siblings. The description covers the resource and data scope but leaves the agent without enough to call it correctly or choose it confidently.

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%, so the description must carry the burden of explaining limit, query, and offset. It mentions none of them, leaving the agent to infer that 'query' is a search filter and that 'limit'/'offset' paginate — neither is stated anywhere.

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 ('Read') and resource ('document portal user metadata'), so the agent knows exactly what is returned. It does not, however, differentiate itself from the close sibling 'list_tenant_user_metadata' or 'list_oauth_app_metadata', which an agent would need to tell apart.

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 many other metadata listing tools, no prerequisites, and no exclusion criteria. 'Through the existing application' gestures at context but does not guide tool selection.

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