list_property_values

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals key behaviors: array-valued properties count each element, results are ordered by frequency, and pagination via limit/offset. However, it does not mention scope (e.g., vault-wide) or any side effects, though the tool appears read-only.

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 extremely concise: three short sentences that front-load the purpose and add essential detail on array handling and ordering. Every sentence serves a purpose with no redundancy.

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?

Given the simple tool with 3 parameters, no output schema, and no annotations, the description reasonably covers purpose, output format, ordering, and counting behavior. It is complete enough for an agent to use correctly, though it could mention what happens if the property does not exist (likely empty list).

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%, providing baseline at 3. The description adds value by explaining that 'Array-valued properties count each element' for the 'key' parameter, and implicitly links 'most frequent first' to ordering related to the key. This extra context exceeds the schema.

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 states the verb 'List' and the resource 'distinct values of one frontmatter property' with output format '{value, count} rows, most frequent first'. It also adds 'A faceted index for a single key', distinguishing it from siblings like list_properties and get_property.

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 provides clear context for when to use the tool (to list distinct values of a property with counts), but does not explicitly mention when not to use it or present alternatives among the sibling tools. The context is sufficient for an agent to decide, but lacks explicit exclusions.

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