get_honors_status

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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement ('Requires being logged in'), which is a key behavioral trait. However, it lacks details on rate limits, error handling, or response format, leaving gaps in behavioral context for a tool that fetches sensitive account data.

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 sentences, front-loaded with the core purpose and followed by a prerequisite. Every sentence earns its place by providing essential information without redundancy or fluff, making it highly efficient and well-structured.

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 complexity (fetching membership data) and lack of annotations and output schema, the description is moderately complete. It covers the what and a key prerequisite, but does not explain the return values or potential errors, which are important for a tool handling user account information without structured output documentation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and usage. This meets the baseline for zero-parameter tools, but does not add extra semantic value 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?

The description clearly states the specific verb ('Check') and resource ('Hilton Honors membership status'), listing exactly what information is retrieved: points balance, tier level, lifetime points, and progress toward next tier. It distinguishes from siblings like 'hilton_status' (likely general account status) and 'get_stay_history' (historical stays).

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 explicitly states 'Requires being logged in,' providing clear context for when to use (after authentication). However, it does not specify when not to use or name alternatives among siblings, such as how this differs from 'hilton_status' or 'get_reservation' for other account details.

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