get_rental_policies

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

No annotations are provided, so the description carries full burden. It states 'retrieve' which implies a read operation, but doesn't disclose behavioral traits such as whether it requires authentication, rate limits, error handling, or what the return format looks like (e.g., structured data vs. text). For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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?

Single sentence, front-loaded with the core purpose, efficiently lists key policy aspects without redundancy. Every word earns its place by specifying what policies are included, making it appropriately sized and easy to scan.

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 no annotations, no output schema, and 3 parameters with incomplete schema coverage, the description is inadequate. It doesn't explain return values, error cases, or behavioral context needed for a tool that retrieves complex policy data. For a read operation with potential variability based on inputs, more completeness is required to guide effective use.

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 67% (2 out of 3 parameters have descriptions), with location_id and country documented but vehicle_class lacking a description. The description adds no specific parameter semantics beyond what the schema provides—it doesn't explain how location_id affects policies, what vehicle_class enums mean in context, or default behaviors for country. Baseline 3 is appropriate given moderate schema coverage.

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 verb 'retrieve' and the resource 'Hertz rental policies', with specific examples of what policies are included (age requirements, fuel policy, etc.). It distinguishes from siblings like get_locations or get_vehicle_details by focusing on policies rather than locations or vehicle specs. However, it doesn't explicitly differentiate from get_reservation which might also involve policy details.

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 explicit guidance on when to use this tool versus alternatives like get_reservation (which might include policy info) or search_vehicles (which could relate to policies). The description implies usage for retrieving policy information, but lacks context on prerequisites, timing, or exclusions (e.g., when location-specific policies are needed).

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