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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the pagination behavior ('a page at a time'); it says nothing about result ordering, match semantics (prefix vs substring, case sensitivity), or whether email matching is exact.

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?

A single tight sentence with no filler; the core action leads and the pagination cue trails without padding.

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 4-parameter search tool with no output schema and thin schema descriptions, the definition does the minimum: it conveys what is searched and that results are paged. It omits match behavior, result shape, and how to resume paging, which an agent needs to call it well.

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 only 25% and the sole documented parameter is teamId, described merely as 'Team.', which is uninformative. The description partially compensates by implying search covers name/email and that limit/cursor drive paging, but it leaves the required teamId and cursor semantics to inference.

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?

States a specific verb (find) and resource (team members) plus the matching keys (name or email) and pagination. It implicitly separates itself from a plain listing like list_members by emphasizing search filtering, but it never names that sibling to make the distinction explicit.

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?

Usage is only implied: an agent can infer this is for locating a specific member by name/email rather than enumerating all members. There is no explicit when-to-use/when-not, and no mention of list_members or list_team_invitations as alternatives for enumerating members or pending invites.

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