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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a useful scoping note that uploaded PDF templates are included, but says nothing about pagination behavior or how the optional 'full' flag changes the response, which are real behavioral considerations.

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?

A single, front-loaded sentence with no wasted words. Efficient, though its brevity contributes to the missing usage and parameter context.

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?

An output schema exists, so return values need not be explained, and the nested pagination/full params are documented in the schema. Still, for a tool whose 'full' flag materially changes the shape and volume of results, the description leaves the agent without any high-level cue about pagination or response richness.

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?

The single top-level queryParams parameter has no description and the reported schema description coverage is 0%. The description mentions no parameters at all, so it does not compensate for the gap around pagination and the type-specific 'full' expansion, even though the nested schema properties happen to carry descriptions.

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 (list) and resource (agreement templates) and scopes it by noting uploaded PDF templates are included. However, it does not distinguish itself from close siblings such as list-custom-templates or list-agreement-types, so an agent cannot route between them on the description alone.

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 guidance on when to use this tool versus alternatives like list-custom-templates or get-template, and no stated prerequisites or exclusions. The agent must infer usage purely from the name.

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