propertyValues

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

Annotations already declare readOnly/non-destructive/non-openWorld, and the description adds real value beyond them by disclosing the conditional return shape by property type ({min,max} vs. distinct-value list) and noting that aggregation is unnecessary. It does not mention pagination interaction with skip/limit beyond what the schema says.

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?

Front-loaded with the core purpose, then structured bullets for the type-dependent behavior and an ordered workflow. Slightly verbose, but each sentence carries actionable information 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?

With annotations, a full output schema, and 100% schema coverage, the remaining gaps are covered by the description's type-branching and workflow guidance. An agent can select and invoke this tool correctly from the definition alone.

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 100%, so the schema already documents all five parameters. The description adds only the provenance of propertyId (the id from findProperties), which is useful but minimal; baseline 3 applies when the schema does the heavy lifting.

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 statistics / distinct values) and resource (a specific property), and crucially explains that behavior branches by property type. This distinguishes it clearly from findProperties, whose id it consumes.

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?

Gives explicit when-to-use branching: number/datetime for range/min/max/spread questions with a note that no aggregation is needed, string/boolean for canonicalizing filter values. It also spells out a 3-step workflow (findLabels → findProperties → this tool) for range questions.

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