get_guest_by_id

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds 'detailed' to suggest a comprehensive profile but does not disclose other behavioral traits such as error handling, permissions, or response structure.

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 with no redundancy. It front-loads the action ('Get'), the resource ('guest profile'), and the condition ('by guest ID'), making it compact and effective.

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 one-parameter getter, the description is complete given the annotations and schema. It states the operation, the parameter condition, and the expected outcome ('detailed profile'), and with no output schema, a return value is intuitively understood.

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 coverage is 100% with the single parameter 'guestId' fully described. The phrase 'by guest ID' in the description merely echoes the schema's 'The guest ID' and adds no new semantic meaning.

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 'get' and identifies the resource as 'guest profile' with the parameter 'guest ID'. It clearly distinguishes from sibling get_guests (plural) by focusing on a single detailed record.

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 implies usage when a guest ID is available but does not explicitly mention alternatives or when not to use it. The sibling get_guests is an obvious alternative for listing, but the description does not reference it, providing only implied guidance.

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