plu_get_property

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

With no annotations, the description carries the full burden. It discloses rate-limiting behavior and server throttling/retry, adding value. However, it does not mention other behavioral aspects such as authentication requirements, side effects, or whether the response is cached, missing some 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 two sentences: the first states the purpose, the second provides essential usage guidance. It is front-loaded and contains no redundant information, earning high marks for conciseness.

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 simplicity (single parameter, public page), the description covers the basic purpose and a key behavioral consideration. However, it omits information about return structure, authentication context, and how 'public page' affects access, making it somewhat incomplete for an agent lacking output schema.

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 coverage is 100% with a clear description for the single parameter 'propertyId'. The description adds no additional meaning beyond 'by ID', so it does not enhance understanding of parameter semantics 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 clearly states the action ('Get property details') and the resource ('by ID') with context ('public page'). It distinguishes from siblings like plu_get_my_properties and plu_search_homes, providing a specific verb-resource pair.

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 rate-limiting guidance and advises sequential calls, which is implicit usage context. However, it does not explicitly state when to use this tool versus alternatives like plu_get_my_properties or when authentication is needed, leaving comparative guidance absent.

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