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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful operational detail beyond that: non-ephemeral filtering, newest-first ordering, the permission requirement, and keyset pagination via nextCursor/cursor. It stops short of describing response item structure or rate 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?

The description is front-loaded with purpose and permission, then compactly covers scope, ordering, type filtering, and pagination. Every sentence carries information and there is no filler.

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 paginated list tool with no output schema, the description covers the important invocation details: scope, ordering, filtering, and cursor-based pagination. It does not describe the shape of returned target objects, but that is a minor omission relative to the schema and annotation 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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaningful nuance: it explains that `type` uses the create vocabulary and that `ios` is listed but not creatable, and it maps `nextCursor` to the cursor query parameter. It does not add much beyond the schema for `limit` or `projectId`.

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 and resource: it lists non-ephemeral saved targets for the key's project. It also specifies ordering (newest first), which distinguishes it from a single-target getter like get_target and from scan-listing siblings.

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?

It clearly establishes the context in which to use the tool: fetching saved targets within the key's project. It does not explicitly name alternatives such as get_target or list_scans, nor does it state when not to use it, but the scope is clear enough for an agent to select it correctly.

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