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

Annotations already mark the call read-only, and the description goes beyond them by clarifying what is returned (bounded members, pins, saved-query references), that truncation is explicit, and that saved-query execution is absent. This adds meaningful behavioral context without contradicting the annotations.

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 sentences with no filler: the first fronts the core read behavior, and the second adds two relevant caveats. Every clause earns its place.

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 low-complexity tool with annotations covering read-only and non-destructive behavior, the description conveys what the return payload covers and flags truncation. With no output schema, a little more detail about response shape or truncation mechanics would make it fully complete, but nothing essential is missing for calling it correctly.

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?

With schema_description_coverage at 0%, the description needed to explain list_id but does not mention it at all. The only implicit link is 'a List', which does not compensate for the lack of detail about how the parameter identifies the resource or any constraints beyond the UUID pattern.

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?

The description states a specific verb ('Read') and a specific object: a List plus its bounded author/asset members, pins, and saved-query references. It also draws a clear boundary by noting saved-query execution is not implemented here, which helps separate it from execution-style or query-style sibling tools.

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?

The read purpose is clear, and the saved-query caveat gives a useful when-not signal. However, the description never names an alternative tool for executing saved queries and gives no explicit conditions for choosing this over related tools such as list_lists or query_list_activity.

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