get-property

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the data included (adverts, price history, photos, contact info, transit stations), which gives useful context. However, it does not disclose potential error cases, authorization requirements, or whether the operation is strictly read-only, leaving some transparency gaps.

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, focused sentence that front-loads the purpose ('Get full details for a single property') and then lists specifics. Every clause adds value with no filler.

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 lookup tool, the description is largely complete: it names the input (UUID) and describes the output scope in enough detail to inform use. While there is no output schema, the enumerated content list compensates. Minor lack of error/edge-case handling prevents a perfect 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 schema already documents the sole parameter 'id' as 'Property UUID', and the description reinforces that by saying 'by UUID.' Since schema description coverage is 100%, the description adds no additional parameter-level meaning beyond emphasizing the identifier's role.

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 uses a specific verb 'Get' with a clear resource 'single property by UUID' and enumerates the scope: 'full details ... including all adverts, price history events, photos, contact info, and nearby transit stations.' This distinguishes it from sibling tools like search-properties and get-points-of-interest, which target different operations or resources.

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 phrase 'by UUID' implicitly tells the agent to use this when a known property ID is available, but there is no explicit statement about when to prefer it over siblings such as search-properties or find-similar-properties. No exclusions or alternative conditions are given.

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