REP Helper

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

The readOnlyHint annotation confirms this is a safe read operation, which the description does not contradict. However, the description adds no behavioral context beyond what the schema and annotations provide (e.g., what happens if the ID is invalid, what fields are returned, or caching behavior).

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 with no filler words. It is front-loaded with the action ('Get') and immediately qualifies the scope ('single rental property by its ID'), 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?

Given the tool's low complexity (one simple string parameter, no nested objects) and the presence of readOnly annotations, the description is sufficient for invocation. However, the lack of an output schema means the description could have clarified the return structure (e.g., 'returns property details').

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 property ID'), the schema fully documents the parameter. The description mentions 'by its ID' but adds no additional semantic information (format constraints, where to find the ID, examples) beyond the schema baseline.

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 retrieves a 'single rental property' using its ID, distinguishing it from the sibling list_properties tool (which handles multiple items). However, it does not explicitly name sibling alternatives like list_properties or differentiate from get_activity.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'use list_properties if you don't have an ID'), nor does it mention prerequisites or error conditions like 'property not found'.

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