dss_list_organizations

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

No annotations are provided, so the description must carry the burden. The verb 'List' communicates a read-only behavior, which is useful but minimal. It does not disclose additional traits like return format, pagination, or authorization needs, but for a simple list operation this may be sufficient.

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 sentence, front-loaded with the verb, with no filler words. Every word contributes to meaning, making it highly concise and well-structured.

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 well-described parameter and no output schema. The description explains what it does and in which system, and the schema covers the required input. It does not detail return values, but for a straightforward list operation, the provided information is reasonably 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?

Schema coverage is 100%: the single parameter device_id is fully described as 'Dahua DSS device ID'. The description adds no extra parameter-specific detail (e.g., how device_id relates to organizations), so it meets the baseline for high schema coverage without enhancing it.

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 target resource ('organizations/groups'), and the context ('in Dahua DSS'), with a specific verb+resource structure. It distinguishes from sibling tools like dss_list_devices and dss_list_channels by naming the organization/group resource.

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 usage by specifying the resource type but provides no explicit when-to-use vs alternatives or exclusions. The context of sibling tools makes it inferable, but there is no direct guidance such as 'use this to list organizations, not channels'.

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