list_profiles

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

With no annotations, the description carries the burden of disclosing behavior. It adds pagination details (50 per page, cursor usage) beyond the schema, and includes the clarification that customer profiles include contacts/customers. It does not mention rate limits or sorting, but for a simple list it provides key behavioral context.

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 two sentences, front-loaded with the core purpose, and every word earns its place. No fluff or repetition beyond the needed clarification of 'contacts/customers'.

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?

Given an output schema exists, the description doesn't need to enumerate return fields. It covers the main purpose and pagination behavior sufficiently. It doesn't mention filtering or sorting, but those are not implied by the schema. A slightly more explicit note about being the list-counterpart to get_profile would push it to 5.

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 only parameter, cursor, is given clear meaning: it comes from the prior response and is used to page forward. Schema description coverage is 0%, so the description fully compensates by explaining how to obtain and use the cursor.

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 uses a specific verb ('List') and identifies the resource ('customer profiles') with clarification ('contacts/customers'). It also states the pagination limit (50 per page), making the tool's function unmistakable. It is clearly distinct from siblings like get_profile or list_products.

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 description clearly indicates how to use the tool for pagination ('Page forward with cursor from the prior response'), providing context on the only parameter. It does not explicitly mention alternatives or when-not-to-use, but the context is clear enough for a list operation.

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