get_rental

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states what the tool does and its return type, without mentioning error handling, auth requirements, side effects, or any constraints. This is a significant gap for a tool with no annotation support.

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 extremely concise, with three short sections (description, args, returns). Every sentence serves a purpose, and there is no fluff or repetition. It is well-structured and front-loaded.

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 get-by-ID tool, the description covers the essential purpose and return type. An output schema exists, so detailed return values need not be explained. However, it lacks any context about how to obtain the property_id or what happens for invalid IDs, which leaves a minor completeness gap.

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 zero description coverage, so the description must compensate. It provides a brief explanation 'property_id: The property ID', which clarifies the parameter's meaning but adds no extra depth beyond what the schema already implies by name and type.

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 'Get a specific rental property by ID', using a specific verb (get), resource (rental property), and scope (by ID). This distinguishes it from sibling tools like list_rentals, create_rental, and get_rental_unit.

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 you have a property ID, but doesn't explicitly state when to use it vs alternatives like list_rentals. No exclusions or alternative tool mentions are provided, leaving usage guidance mainly implicit.

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