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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that these are home-info UDFs (Year, Manufacturer, Serial/VIN, Payoff), but says nothing about auth requirements, missing-unit behavior, or which identifier wins when several are supplied.

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?

A single compact sentence, front-loaded with the resource and scope. The trailing ellipsis in the examples adds little but costs almost nothing.

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?

An output schema exists so return values need not be described, but the definition leaves the identifying-parameter question unanswered and provides no routing to sibling UDF tools, which is the main thing an agent needs for a four-optional-parameter lookup.

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 0% and all four parameters (unit_id, shortname, unit_name, property_id) carry no descriptions. The description adds no parameter meaning at all, and critically no guidance on which of these optional-looking identifiers actually identifies the unit. With four competing lookup keys and zero required parameters, this is a real gap.

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?

States a specific resource (unit-level UDFs) and scopes it with 'for one unit', which implicitly separates it from get_property_udfs, get_tenant_udfs, and get_marketing_udfs. The parenthetical examples (Year, Manufacturer, Serial/VIN, Payoff) make the domain concrete, though the verb 'get' is only implied by the name.

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?

No statement of when to use this versus the other *_udfs siblings, no prerequisites, and no note on how to identify the target unit. The agent must infer everything from the resource noun alone.

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