search_contact_people

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

The description only states 'search for people by name', with no additional behavioral traits like pagination, search algorithm (exact match vs fuzzy), or result limits. Annotations provide openWorldHint, but the description adds no context about what that implies for results.

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, front-loaded sentence with no redundant information. Every word serves a purpose, making it efficient and easy to parse.

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?

The description is minimally adequate for a simple search with one parameter, but lacks details about return values (e.g., list of people, fields returned) and behavioral context (e.g., ordering, pagination). Without an output schema, the description should clarify what the agent can expect.

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 documentation coverage is 0% (the 'search' parameter has no description). The description adds 'by name', hinting that the parameter expects a name string, but does not specify format, case sensitivity, or partial matching behavior. It adds some meaning beyond the schema but is insufficient for full clarity.

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 clearly states it searches for people by name in contacts, using a specific verb and resource. It distinguishes from sibling tools like search_contact_organisations (organisations vs people) and get_contact_details (which likely retrieves a specific contact's details).

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?

No guidance on when to use this tool versus alternatives. It does not mention when not to use it or provide context about search scope, such as whether it includes archived contacts or external sources. Sibling tools exist but no difference is highlighted.

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