trmm_list_clients_sites

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minor context by indicating the returned data includes IDs intended for filtering, but it does not disclose other behavioral traits such as pagination, nesting, or completeness beyond the word 'All.'

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, tightly scoped sentence with no filler. The core information is front-loaded, and the filtering purpose is appended efficiently.

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?

For a zero-parameter, read-only list tool, the description covers what is returned and why the results matter. It does not explicitly describe the return shape beyond 'clients and their sites,' and there is no output schema to fill that gap, but the tool is simple enough that this is nearly 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?

This tool has zero parameters and the schema is trivially complete, so there are no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description's mention of IDs for filtering refers to output rather than input, which is acceptable in this case.

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 states the exact resource ('clients and their sites') and the key selling point (ids for filtering). It is clearly distinct from siblings like trmm_list_agents, trmm_list_alerts, and trmm_list_scripts because it names a different entity. The verb is implied by the tool name and the noun-phrase description, but the meaning is 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 phrase 'with ids for filtering' implies this tool should be used to retrieve client/site IDs for use as filters in other endpoints. However, the description does not explicitly say when to choose this tool over alternatives, nor does it name any sibling tools or exclusions.

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