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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it implies a read-only lookup but says nothing about search scope, partial-match behavior, result caps, permissions, or pagination. Only the "name or email fragment" phrase hints at matching semantics.

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 efficient sentence with the search dimensions front-loaded and no filler. It is concise, but the brevity comes at the cost of the content the other dimensions need.

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 tool with no annotations, no output schema, low schema coverage, and ambiguous paging parameters, this one-line description is far too thin. An agent cannot tell what a result set looks like, how paging works, or whether the search spans all workspaces.

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% (only notification_message is documented), so the description must compensate and does not. It loosely maps to search_query but leaves people_page and people_count — both typed as strings, which is itself surprising for paging parameters — entirely unexplained in either location.

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 gives a specific verb and resource ("Search people") plus the matching dimensions (name or email fragment), which is clearly more informative than the bare name. It does not, however, differentiate this tool from sibling list_workspace_users or explain how the two overlap, so the agent is left to infer the distinction from names alone.

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?

There is no statement of when to use this versus alternatives such as list_workspace_users, nor any preconditions (required permissions, scope of the search across workspaces or channels). The agent must guess the routing.

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