ywm_list_owners

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

No annotations exist, so the description carries full burden. It states 'List' implying read-only, but no details on authentication requirements, rate limits, response structure, or potential side effects. The behavior is minimally disclosed.

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 short (three words), making it concise but at the cost of missing essential information. While no words are wasted, it is under-specified for an agent to use effectively. A balance between brevity and completeness is needed.

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 no output schema and no annotations, the description should provide more context, such as what the output contains (e.g., list of owner IDs or names) or behavior for missing host_id. It currently leaves significant gaps for an agent to infer correctly.

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% with one parameter (host_id) fully described in the schema. The description does not add any additional meaning or usage hints beyond what the schema provides. Baseline 3 applies because the schema already documents the parameter adequately.

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 host owners' is a specific verb+resource pair, clearly indicating the action and target. It distinguishes from siblings like ywm_list_hosts by focusing on 'owners' rather than hosts themselves. However, it does not clarify what 'owners' means (e.g., user accounts), which limits clarity.

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 on when to use this tool versus alternatives like ywm_list_hosts. The description lacks context on prerequisites (e.g., host_id required) or situations where this tool is appropriate. The sibling list includes many tools, but no differentiation is provided.

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