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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of match semantics (substring vs prefix), case sensitivity, or what an empty result means, which is the value it could have added.

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 first sentence is tight and front-loaded. The second sentence is a garbled fragment that does not earn its place and actively dilutes an otherwise clean definition.

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?

This is a simple, well-annotated, fully documented read tool with no output schema, so little is required. The real gap is the intended routing to vision_list_clients, which is present only as an unreadable fragment, leaving the agent without the one piece of context that is not already in structured fields.

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 100%: 'text', 'limit', and 'offset' are each documented with bounds and defaults. The description's 'by name or email text' only echoes the existing 'text' parameter description, so baseline 3 applies.

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 first sentence gives a specific verb and resource ('Search clients') plus the two searchable fields (name, email), which is enough to distinguish it from a plain list. The trailing fragment 'client / list_clients.' gestures at a sibling but is too broken to serve as clean differentiation.

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 explicit statement of when to use this versus vision_list_clients; the only signal is the malformed fragment 'client / list_clients.', which reads as truncated text rather than an instruction. An agent must guess that this tool requires a search term while the sibling does not.

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