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

With no annotations provided, the description carries the full burden for behavioral disclosure. 'List' implies a read-only operation, but it does not mention pagination, return format, error behavior, or any side effects. It does not contradict anything, but it also does not add depth beyond the basic verb.

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 a single, efficient sentence that front-loads the core action and then adds the optional search capability. There is no fluff or repetition, and it is appropriately concise for the tool's simplicity.

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 no output schema and no annotations, the description is incomplete. It does not state what the returned list contains (e.g., profile objects), nor does it mention pagination or behavior when no results. It also fails to contextualize when to use this over sibling tools, leaving the agent without enough information for confident invocation.

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 description coverage is 0%, so the description must compensate. It adds meaning to the 'search' parameter by stating it can filter by name or email, which is helpful. However, it does not explain the 'limit' parameter, leaving it entirely to inference. Since only half of the parameters are described, the compensation is insufficient.

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 clear action ('List') and a specific resource ('the user's saved people'), which distinguishes it from singular get_profile/get_my_profile. However, it does not explicitly differentiate from list_relationships or mention the difference between 'saved people' and other profile types, so it is clear but not fully distinguishing.

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 gives no guidance on when to use this tool versus alternatives like get_profile or list_relationships. It only mentions optional search, which is parameter behavior, not usage context. There is no mention of prerequisites or scenarios where this tool is preferred.

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