Get Guest

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds that the return is 'full contact record', which gives useful context about the output, but doesn't discuss errors, rate limits, or other behavioral nuances. This is acceptable but not exceptional.

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 a single sentence of nine words. It is front-loaded with the verb 'Fetch', states the object, and adds a parenthetical specifying the return detail. There is zero redundancy.

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 one-parameter GET-by-id tool with rich annotations (read-only, idempotent), the description plus schema cover everything needed. The 'full contact record' parenthetical preempts questions about the return shape, and there is no output schema requirement. The tool is simple enough that the description is complete.

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?

The schema has no description, so coverage is 0%. The description's 'by id' clarifies that the generic 'id' parameter refers to the guest's identifier, which adds semantic meaning. With only one integer parameter and a straightforward purpose, this is sufficient compensation.

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 the specific verb 'Fetch' and names the exact resource 'a single guest by id', further clarifying the scope as 'full contact record'. This clearly distinguishes it from sibling tools like ownerrez_search_guests (search) and ownerrez_get_owner (different entity).

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 conveys the use case: retrieving a single guest when you have the guest's numeric id. It does not explicitly state when not to use it or mention alternatives, but the context is unambiguous given the sibling list and the 'by id' qualifier.

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