Get Property

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

With no annotations to rely on, the description discloses key behaviors: it lists the types of data returned and states the result 'displays on an interactive map.' This goes beyond a minimal 'get' statement, though it stops short of explicitly noting read-only status or potential edge cases.

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, front-loaded with the verb and resource, and every word adds value. No filler or redundant repetition of the title 'Get Property.'

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 tool with 3 parameters and no output schema, the description covers the core purpose and output presentation. It lacks explicit differentiation from sibling tools but is otherwise complete for typical use.

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?

Input schema has 100% description coverage for all three parameters, so a baseline of 3 applies. The description mentions fields like owner and zoning but does not add meaningful parameter-level syntax or relationships beyond the schema's one-line labels.

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 specifies the tool's function: 'Get detailed property information including owner, units, zoning, coordinates, and rent stabilization analysis.' This distinguishes it from sibling search tools by emphasizing a single property's comprehensive detail, though it does not explicitly name siblings.

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—call this when you need detailed data for a specific property—but provides no explicit guidance on when to choose it over search_properties, search_sales, or other siblings. No exclusions or alternative scenarios are mentioned.

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