propertieslist

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'options and filters' but fails to describe key behaviors such as pagination (implied by parameters), rate limits, authentication needs, or what the output looks like (e.g., list format). This is inadequate for a tool with 20 parameters and no output schema.

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 a single, efficient sentence with no wasted words, making it front-loaded and easy to parse. However, it could be more structured by explicitly mentioning key aspects like pagination or filtering scope to improve clarity without losing conciseness.

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 complexity (20 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's behavior, output format, or usage context, leaving significant gaps for an agent to understand how to invoke it effectively. More detail is needed to compensate for the lack of structured metadata.

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 fully documents all 20 parameters with descriptions, defaults, and examples. The description adds no additional meaning beyond implying filtering capabilities, which is already covered in the schema. Baseline 3 is appropriate as 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?

The description 'List properties with options and filters' clearly indicates a listing operation on properties, but it's vague about what 'options and filters' entail and doesn't differentiate from sibling tools like 'propertiesdetail' or 'propertiesv3lookup'. It states the basic verb+resource but lacks specificity about scope or distinction.

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 guidance is provided on when to use this tool versus alternatives like 'propertiesdetail' for individual properties or 'propertiesv3lookup' for other property operations. The description implies filtering capabilities but doesn't specify contexts or exclusions, leaving usage unclear.

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