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

The readOnlyHint annotation already establishes that this is a safe, non-mutating read, so the description's burden is lower. It adds the underlying REST endpoint (GET /v1/rentals/{propertyId}), which is mildly useful for tracing, but discloses nothing about error behavior (e.g., 404 on unknown id) or auth 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?

Two short, front-loaded sentences with zero filler: the action comes first and the endpoint mapping is a compact trailing clause. Nothing needs trimming.

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 single-parameter read tool with readOnlyHint coverage this is close to adequate, but no output schema exists, so the description should ideally say something about what is returned or what the caller can expect on failure. It leaves the agent to guess at the response shape.

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% and the single property_id parameter is already documented in the schema, so the schema carries the parameter semantics. The description only restates 'by id' and adds no format, range, or sourcing detail 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 states a specific verb (Fetch) and resource (one rental property) scoped by id, and the word 'one' implicitly separates it from the sibling buildium_list_rental_properties. It does not explicitly name the sibling, so it falls just short of full sibling differentiation.

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?

Usage is only implied: 'by id' tells the agent this is a point lookup rather than a search or list, which is sufficient for such a simple tool. However, there is no explicit when-to-use guidance, no mention of the list sibling as the alternative, and no note about what happens when the id is invalid.

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