find_guest

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The note that 'OwnerRez bounds this endpoint by created_since_utc' is a genuine and useful constraint disclosure, but the description omits read-only safety, pagination behavior, ordering, and what happens when max_items is reached. For a zero-annotation tool, this is a substantial gap.

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?

Two sentences with the core purpose front-loaded and no filler. The second sentence is slightly indirect, attributing the constraint to 'OwnerRez' rather than describing the tool's behavior directly, but it earns its place as a meaningful caveat.

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?

An output schema exists and all parameters are documented, so return values and parameter semantics are largely covered. The description is adequate for a simple search/list tool but misses explicit usage guidance and behavioral detail such as pagination, and the absence of annotations raises the burden the description must carry.

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 the schema already documents all three parameters, giving a baseline of 3. The description adds minor value by framing created_since_utc as an endpoint-level bound rather than just a parameter default, but it adds nothing about query or max_items beyond 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?

'Search or list guests' is a specific verb+resource statement that clearly identifies what the tool does and covers both operating modes (search by query, list all). It doesn't explicitly name sibling tools for differentiation, but no sibling in the provided set is guest-related, so the tool is naturally distinct.

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 when-to-use guidance is provided. There is no mention of alternatives, prerequisites, or conditions that should select this tool over others. 'Search or list guests' carries only the barest implication of usage, with no guidance on when to search versus list or what to do when results are bounded.

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