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

Annotations already declare readOnlyHint=true and the title "Get vendor", so the safety profile is covered. The description adds nothing beyond that — no information on not-found behavior, permission requirements, or what a vendor record contains — making it essentially a restatement of the annotated title.

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 short sentence with zero filler, front-loading the verb and resource. Nothing could be removed without losing meaning.

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 single-record read with a complete schema and readOnly annotation, the essentials are present, and no output schema exists so return values need not be described. However, an agent gets no signal about not-found handling or which fields come back, leaving a small but real gap.

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?

Only one parameter, and the schema fully documents it at 100% coverage (numeric string ID preserving 64-bit precision). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 verb (get) and resource (vendor) with a retrieval key (by ID), which cleanly separates it from propertyware_list_vendors. It stops short of naming the sibling, but the singular-vs-list distinction is evident.

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 ID" implies the precondition (you already have a numeric vendor ID) and usage is inferable, but there is no explicit when-to-use guidance, no mention of the list_vendors alternative for lookup/discovery, and no statement about behavior when the ID does not exist.

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