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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral detail beyond that: the output shape changes based on the class argument (per-class aggregates with n_paths/n_with_value_max vs. per-path fill rate and level). The trailing "Read-only" merely restates annotations, and it does not mention cost or size of the result, which matters for a whole-file inventory.

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?

It is front-loaded and free of filler, but the semicolon-chained clauses and the garbled fragment "the ones where, fields and set_properties take" make it harder to parse than necessary. A single sentence with the class/no-class output distinction split out would read far cleaner.

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 no output schema, the description carries the burden of describing return values, and it does so for both the class and no-class cases, including the metric names. The only meaningful gap is include_empty behavior and any indication of result size, which are minor for a two-optional-parameter read-only tool.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining the semantic effect of omitting class (sets only) versus supplying it (every path with fill rate and level, type or occurrence). It says nothing about include_empty, which is left entirely to 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 opening clause names the exact resources (property sets, properties, quantity sets) and the scope ("IN THIS FILE", per class), which is a specific inventory operation rather than a generic list. It is clearly distinguishable from set_properties, which the description explicitly points at as the write-side counterpart.

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?

It gives an explicit when-to-use rule: "Use it before filtering or writing a property", and names the downstream tools (where, fields, set_properties) that consume the returned paths. It does not state when not to use it or what to do if the caller already knows the paths, so it stops short of full routing guidance.

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