listDevices

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

With no annotations provided, the description carries the full disclosure burden, yet it only states the core action. It does not reveal that siteId is effectively required despite the schema listing no required fields, nor does it mention return format, pagination, or behavior on invalid site IDs. The verb 'List' weakly implies a read operation, but little else is transparent.

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 eight-word sentence with zero filler, and the verb and resource are front-loaded. It is efficiently written, though the brevity partly reflects how little behavioral information is offered.

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 tool with no annotations and no output schema, more than this is needed: the schema marks siteId as not required while the description implies a site must be specified, and nothing disambiguates this from searchDevices or listDevicesStats. The single-parameter surface keeps it from being a 1, but the gaps are material.

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 0%, so the description must compensate. It partially does: 'for a specific site' tells the agent that siteId scopes the listing. However, it does not clarify the ID format or how to obtain it; with only one well-named parameter, this is a moderate gap rather than a severe one.

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 names a specific verb ('List'), a specific resource ('provisioned network devices'), and a scope ('for a specific site'), so an agent can immediately grasp the tool's function. It is not a tautology and reads distinctly from siblings, though it does not explicitly name alternatives like searchDevices or listDevicesStats.

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?

There is no guidance on when to use listDevices versus overlapping siblings such as searchDevices, listDevicesStats, or getDevice. The phrase 'for a specific site' is a weak contextual hint that the tool is site-scoped, but no conditions, exclusions, or alternatives are stated.

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