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

With readOnlyHint/destructiveHint already covering the safety profile, the description still adds real context: it will not re-run checks (so results may be stale relative to the current file) and the POST requires an OAuth bearer token with scope 'lender'. It stops short of describing what the returned package contains or any size/pagination limits.

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?

Four short sentences with zero filler, and the core action is front-loaded before the behavioral and auth caveats. The 'POST' phrasing is slightly awkward for a read tool but not wasteful.

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?

Coverage of auth, idempotency, and identifier choice is good, but with no output schema and no parameter descriptions the caller is left without any sense of what a package response contains or how ambiguity in the two identifiers resolves. Adequate but with clear gaps.

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 0%, so the description must carry parameter meaning. It does clarify that packageId and caseId are alternative lookup keys scoped to the caller's workspace, but it never explains the difference between a package and a case identifier, which one wins if both are supplied, or any expected format.

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 an underwriting package') and adds a scoping clause ('Does not re-run the checks') that separates it from the write-side sibling start_underwriting_package. It does not explicitly name read_case vs read_package, so the sibling differentiation is only partial.

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?

'Does not re-run the checks' implies you should go elsewhere (likely start_underwriting_package) to execute checks, and 'Pass packageId or caseId' tells the caller either identifier works. However, no alternative tool is named and no when-not condition, precedence rule, or behavior for passing both/neither is given.

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