List Properties

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

Annotations already declare the tool read-only and idempotent. The description adds useful behavioral context about the default compact view, the full=true switch, and the use of limit to cap results, which informs expected behavior without contradicting annotations.

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 compact and front-loaded, with the core action stated first followed by relevant output and parameter behavior. Every clause adds value without 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 absence of an output schema, the description lists the compact view fields and explains the full option, covering the main use cases. It misses semantics for include_tags and include_fields, but overall it provides sufficient context for an agent to understand the tool's purpose and basic behavior.

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?

The description elaborates on the full and limit parameters, explaining what full=true does and how limit caps results, which goes slightly beyond the schema descriptions. However, it provides no information about include_tags and include_fields, leaving those parameters ambiguous.

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 tool lists properties, with a specific verb and resource. It also provides details about the compact view and full option, giving scope beyond a simple 'list'. While it doesn't explicitly contrast with get_property, the naming and behavior are unambiguous.

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 implies when to use the tool (to retrieve multiple properties) and mentions options like full and limit, but does not explicitly compare with sibling tools like get_property. There is no exclusionary guidance such as 'for a single property, use get_property instead.'

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