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. The description adds the returned field set and the underlying endpoint (POST groups/search), which is useful context, but says nothing about result ordering or that the call is capped with no paging — that only appears in the schema.

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?

Three terse sentences: what it searches, what it returns, what it calls. Searchable fields are front-loaded and no sentence is filler.

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?

With no output schema, the explicit return-field list (id, name, type, phone) is exactly the missing piece and is present. A note on result ordering or the practical consequence of the no-paging cap would complete it, but nothing essential for a correct call is absent.

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 60%; type, limit and updated_since are documented in the schema, while group_name and business_phone are bare. The description's "by name, type or phone" maps to three of the five parameters, but it ignores updated_since and limit entirely, so it does not compensate for the coverage gap.

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?

Specific verb + resource ("Search groups"), plus a clarifying gloss that groups are employer/business accounts, and an enumeration of the searchable fields and returned fields. It is clearly distinguishable from the get_group/create_group siblings, though it never names them.

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 word "search" plus the searchable-field list implies the use case (look up a group when you don't have its id), but there is no explicit when-to-use/when-not guidance and no pointer to get_group for direct id lookups or to search_individuals for people. Usage is inferred rather than stated.

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