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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the description only needs added context. It delivers that by disclosing the auth prerequisite ('Cotlet API key with access to this app') and the shape of the returned matches, useful for a read tool.

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?

Front-loaded and mostly tight, but the opening clause 'Contacts and companies by name or email...' is partially repeated by 'Searches your CRM by name, company name or email,' costing a little redundancy. Still appropriately sized.

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 description usefully enumerates what comes back (UID, role, company). For a two-parameter search tool, that plus the auth note is nearly complete; only pagination or match-limit behavior is unaddressed.

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 100% and both parameters carry their own descriptions, so the schema does the heavy lifting. The description restates the query surfaces (name, company name, email) and the role values, matching but not extending the schema.

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 (searches/finds) and resource (contacts and companies), and describes the return payload (UID, role, company). An agent can distinguish it from suitedash_create_contact and the list_* siblings without opening a schema.

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?

Gives clear operating context: 'Use the UID as client_id or contact_id in the other tools,' which tells the agent this is the lookup step feeding subsequent calls. It stops short of naming explicit alternatives or when-not-to-use conditions, so it stays below a 5.

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