list_owners

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

With no annotations, the description must fully disclose behavior. It indicates a read-only list operation, but does not explain pagination limits (despite max_items), sorting, filtering, authorization requirements, or what happens if no owners exist. The behavioral context is minimal.

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, front-loaded sentence with no redundancy. Every word earns its place, and it efficiently conveys the core purpose and return fields.

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?

The tool is simple with one optional parameter and an output schema, so the description captures the essential resource and return fields. However, it omits any explanation of the max_items parameter's effect, which is a minor gap for a tool this simple. The presence of an output schema covers return value details, so the description is largely complete.

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 only parameter, max_items, is completely unexplained in the description. Schema coverage is 0%, so the description carries the burden, but it fails to convey that max_items limits the number of results or how the default affects behavior. The parameter name gives some semantic hints, but the description adds no value.

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 action ('List'), the resource ('property owners'), and the specific fields returned (id, name, contact). It is distinct from siblings like list_properties, which lists properties rather than owners.

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 instead of alternatives. The description does not mention any specific scenarios, prerequisites, or references to sibling tools, leaving the agent without context for selection.

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