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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes one genuine behavioral fact beyond that: results come back in fixed pages of 50. It says nothing about ordering, total counts, or how an agent knows it has reached the last page, which matters for a paging tool.

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 short sentences, zero filler, with the core list-and-paginate fact front-loaded and the workflow hint second. Nothing could be cut without losing information.

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?

The tool is simple (one optional param, no output schema, closed-world), so the low detail is partly defensible. Still, for a paginated read whose output shape is undocumented, an agent is left guessing about ordering, result fields, and termination conditions.

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?

There is a single parameter, offset, with 0% schema description coverage, so the description must carry the load. 'Pages of 50' implicitly explains the offset step size, which is genuinely helpful, but it never states the units, default behavior, or how to detect exhaustion, so meaning is only partially added.

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 opens with a specific verb+resource ('List owned saved profile identities') and adds scope ('owned') and pagination granularity ('pages of 50'), which clearly separates it from write siblings like create/delete_supplier_feed_profile. It stops short of naming the read sibling directly, referring instead to 'a specific profile'.

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?

'Read a specific profile before reusing or approving it' implies the workflow split between this list tool and the get tool, and hints at a prerequisite for approve_supplier_feed_profile. However, the alternative is never named, and there is no guidance on when listing is appropriate versus going straight to get_supplier_feed_profile by id.

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