Search Guests

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so no safety concerns are needed. The description adds meaningful behavioral context: results are compact by default and full=true returns every field. This goes beyond the annotations and helps the agent understand response format variations.

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 two short sentences, front-loaded with the primary function, and every word adds value. It efficiently covers the core behavior without unnecessary fluff.

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?

For a simple search tool with three parameters and no output schema, the description provides sufficient context for correct invocation: what to search, the search parameter, and the full parameter behavior. The only minor gap is lack of explanation for limit, but it is a standard pagination parameter and self-explanatory from its name.

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 only 33% (only q is described). The description clarifies the purpose of q and adds semantics for full (full=true for every field), but does not explain the limit parameter. Since coverage is low, the description should compensate more; it partially does but leaves limit undocumented, resulting in a moderate score.

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 uses a specific verb ('Find') and resource ('guests') with explicit search criteria ('by name or email'). It clearly distinguishes itself from sibling tools like ownerrez_get_guest, which implies retrieval by ID, while this tool searches by name/email.

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 description clearly implies when to use the tool: when you need to find guests by name or email. It does not explicitly mention alternatives or exclusions, but the context is unambiguous and sufficient for an agent to decide.

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