search_coaches_by_name

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

The description is minimal and does not disclose any behavioral traits beyond the literal search action. With no annotations provided, the description fails to convey that this is a read-only operation, how pagination works, or that parameters like include and select affect results. This is critically insufficient.

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 description is extremely concise (one 5-word sentence), but it under-specifies the tool's functionality. Conciseness should not come at the cost of completeness; each word should earn its place, which this single phrase does not.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description is highly incomplete. It does not mention pagination, return format, or the purpose of filtering/includes. It barely explains the core function and provides no context for complex usage.

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%, so each parameter has a description. The tool description adds minimal extra meaning (e.g., 'by name' hints at the primary search parameter). However, it does not explain the role of optional parameters like include, select, or filters, but the schema handles that adequately, so baseline 3 is appropriate.

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 'Search coaches by name,' indicating a search operation on coaches by name. This distinguishes it from siblings like get_all_coaches (retrieves all) and get_coach_by_id (specific ID), though it doesn't explicitly differentiate from other search tools.

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. The description lacks any context about situations where search_coaches_by_name is preferred over get_all_coaches or get_coach_by_id, and provides no exclusions or prerequisites.

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