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

With no annotations provided, the description carries full burden and adds valuable behavioral context beyond the basic action. It discloses the important policy detail about 'No cancellation fee when cancelled before the scheduled pickup time', which is critical for user decision-making. However, it doesn't mention other behavioral aspects like response format, error conditions, or authentication requirements.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second adds critical behavioral context about cancellation fees. There's zero wasted language or 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 mutation tool with no annotations and no output schema, the description does well by including the cancellation fee policy. However, it could be more complete by mentioning what happens after cancellation (confirmation, refund process) or error scenarios. Given the complexity of a cancellation operation, there's room for slightly more context about the outcome.

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?

With 100% schema description coverage, the input schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation but doesn't provide additional semantic context about how parameters interact or special considerations.

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 action ('Cancel') and target resource ('an existing Enterprise reservation'), distinguishing it from sibling tools like 'modify_reservation' or 'create_reservation'. It provides precise scope by specifying 'Enterprise' reservation type.

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 provides clear context for when to use this tool (to cancel reservations) and implicitly distinguishes it from modification tools. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings like 'modify_reservation' for changes instead of cancellation.

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

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

With no annotations provided, the description carries full burden but only states it 'creates' a reservation without disclosing behavioral traits like whether this is a transactional operation, what happens on success/failure, if it requires authentication, or any rate limits. It mentions required inputs but not the operational context.

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, well-structured sentence that efficiently communicates the tool's purpose and key requirements. It is front-loaded with the main action and avoids unnecessary elaboration, making it easy to parse.

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 complex mutation tool with 13 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral aspects, error handling, return values, and doesn't fully compensate for the schema's incomplete coverage, leaving the agent with significant gaps.

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 description lists categories of required inputs (vehicle, location, dates, driver info), which adds some meaning beyond the schema's 62% coverage. However, it doesn't detail specific parameters or their relationships, leaving gaps for the 38% of schema parameters without descriptions (e.g., driver_age, discount_code).

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 action ('Create a new Enterprise Rent-A-Car reservation') and specifies the required components (vehicle selection, location details, dates, driver information). It distinguishes from siblings like 'modify_reservation' and 'cancel_reservation' by focusing on creation, though it doesn't explicitly contrast with them.

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 mentions 'Requires' to list necessary inputs, but provides no guidance on when to use this tool versus alternatives like 'modify_reservation' or 'search_vehicles'. It lacks explicit context about prerequisites or scenarios where this tool is appropriate.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Retrieve') but doesn't specify authentication requirements beyond the parameters, potential rate limits, error conditions, or what happens if credentials are invalid. For a tool requiring sensitive credentials, this is a significant gap in safety and operational context.

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, efficient sentence that front-loads the core purpose and lists included data points without any fluff or redundancy. Every word earns its place, making it easy for an agent to parse quickly.

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 of a credential-based account retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the return values look like (e.g., structured data format), error handling, or security implications, leaving the agent with insufficient context for reliable invocation.

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 input schema fully documents both parameters (enterprise_plus_number and pin) with clear descriptions. The description adds no additional parameter semantics beyond implying these are used for authentication, which is already evident from the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Enterprise Plus account information', specifying what data is included (tier status, rental history, free day certificates). It distinguishes from siblings like get_loyalty_points by focusing on comprehensive account info rather than just points, though it doesn't explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives like get_loyalty_points or other account-related operations. It doesn't mention prerequisites, context for usage, or exclusions, leaving the agent to infer based on parameter requirements alone.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Check') but doesn't explicitly state if it's safe, requires authentication (beyond the parameters), has rate limits, or returns structured data. The description lacks details on error handling, response format, or any side effects, which is a significant gap for a tool with authentication parameters.

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, efficient sentence that front-loads the purpose and lists all retrieved information without unnecessary words. Every element ('balance, tier status, points required for next tier, expiration date, and recent points activity') earns its place by specifying the tool's scope.

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 (authentication parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return values, error cases, or behavioral traits like security requirements, making it inadequate for an agent to fully understand how to invoke and interpret results without additional context.

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 description coverage is 100%, so the input schema already documents both parameters ('enterprise_plus_number' and 'pin') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as format examples or usage context, but it doesn't need to compensate for gaps, so a baseline score of 3 is appropriate.

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 action ('Check') and resource ('Enterprise Plus loyalty points'), listing exactly what information is retrieved: balance, tier status, points for next tier, expiration date, and recent activity. It distinguishes from sibling tools by focusing on loyalty points rather than reservations, accounts, or vehicles.

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 provides no guidance on when to use this tool versus alternatives like 'get_account' or other siblings. It doesn't mention prerequisites, exclusions, or specific contexts where this tool is preferred, leaving the agent to infer usage based on the purpose alone.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information (a read operation) but doesn't address critical aspects like whether this requires authentication, rate limits, error conditions, or what happens with invalid inputs. The description is functional but lacks operational context needed for safe invocation.

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, well-structured sentence that efficiently communicates the core functionality without unnecessary words. It's appropriately front-loaded with the main purpose, though it could potentially be split for even better clarity.

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 tool's complexity (detailed vehicle information with pricing and options), lack of annotations, and absence of an output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, how pricing breakdowns are structured, or what format the response takes. For a tool with two parameters and no structured output documentation, more completeness is needed.

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 description coverage is 100%, so both parameters (vehicle_id, rate_code) are documented in the schema. The description adds minimal value beyond this, mentioning 'specific vehicle' which aligns with vehicle_id and 'pricing breakdown' which hints at rate_code's purpose. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 tool's purpose with specific verbs ('get detailed information', 'full pricing breakdown', 'available protection options') and identifies the target resource ('specific vehicle from search results'). It distinguishes itself from siblings like 'search_vehicles' by focusing on detailed retrieval rather than searching, though it doesn't explicitly contrast with other siblings like 'get_account'.

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 context by specifying 'from search results', suggesting this tool should be used after a search operation. However, it lacks explicit guidance on when to use this versus alternatives like 'get_account' or 'get_loyalty_points', and doesn't mention prerequisites or exclusions beyond the implied vehicle_id requirement.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Modify') but doesn't specify whether this requires authentication, has rate limits, is reversible, or what happens to unchanged fields. For a tool that modifies reservations—a potentially sensitive operation—this lack of detail is a significant 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?

The description is a single, efficient sentence that front-loads the core purpose. Every word contributes meaning without redundancy, making it easy for an agent to parse quickly. No extraneous information is included.

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 of modifying reservations (a mutation with 7 parameters) and the absence of both annotations and an output schema, the description is insufficient. It doesn't cover behavioral aspects like error conditions, success responses, or dependencies, leaving the agent with incomplete context for safe and 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 100%, so the schema fully documents all 7 parameters. The description adds minimal value by hinting at the types of modifications ('dates, locations, or vehicle class'), which aligns with the schema but doesn't provide additional semantics like format examples or constraints. This meets the baseline for high 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 action ('Modify') and resource ('existing Enterprise reservation'), and specifies what can be modified ('change dates, locations, or vehicle class'). It distinguishes from siblings like 'cancel_reservation' and 'create_reservation' by focusing on updates rather than creation or cancellation. However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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 provides no guidance on when to use this tool versus alternatives like 'cancel_reservation' or 'create_reservation'. It doesn't mention prerequisites (e.g., needing an existing reservation) or constraints (e.g., modification policies). Without such context, the agent must infer usage from the tool name alone.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'Returns a list of available cars with pricing and features,' which adds some context on output. However, it fails to disclose critical behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or how results are filtered or sorted, leaving significant gaps for a tool with 10 parameters.

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 appropriately sized with two sentences that are front-loaded: the first sentence states the purpose and scope, and the second explains the return value. There is zero waste, and every sentence earns its place by adding essential information without 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?

Given the complexity of 10 parameters and no output schema, the description is partially complete. It covers the basic purpose and return format but lacks details on behavioral aspects like error handling, pagination, or data freshness. Without annotations, it should provide more context on operational constraints to fully guide an AI agent, resulting in a moderate score.

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 description adds minimal meaning beyond the input schema, which has 100% coverage with detailed parameter descriptions. It mentions 'dates, locations, and preferences,' aligning with parameters like pickup/dropoff and vehicle_class, but does not provide additional syntax, format details, or usage examples. With high schema coverage, the baseline score of 3 is appropriate as the schema does most of the work.

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 action ('Search for available vehicles'), the resource ('at Enterprise Rent-A-Car'), and the scope ('for specific dates, locations, and preferences'). It distinguishes this from siblings like 'create_reservation' or 'get_vehicle_details' by focusing on availability search rather than booking or detailed vehicle information.

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 context through 'Search for available vehicles... for specific dates, locations, and preferences,' suggesting when to use it. However, it lacks explicit guidance on when to choose this tool over alternatives like 'get_vehicle_details' or 'create_reservation,' and does not mention prerequisites or exclusions, leaving some ambiguity.

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