get_site_inventory

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

No annotations are provided, so the description carries the full burden. It communicates that this is a read operation returning a full inventory, but it does not disclose whether the call can be expensive, whether special permissions are required, or how the response is shaped beyond the separate output schema.

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?

Both sentences earn their place: the first states the tool's purpose and scope, and the second defines the only parameter. There is no filler, redundancy, or restatement of the schema.

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 single-parameter read-only endpoint with an output schema, the description is largely sufficient: it identifies the resource, scope, and parameter semantics. It is not fully complete only because it does not hint at when this endpoint is preferable to related list endpoints.

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?

With 0% schema description coverage, the description compensates by defining 'site' as 'site name or ID.' This adds meaningful semantics beyond the bare string type, though it could be richer with more detail about ID format or uniqueness.

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 and resource: 'Get full inventory for a site' and defines its scope as 'all devices and connected clients.' This distinguishes it from siblings like list_site_devices and list_clients by signaling that it returns a combined, site-scoped inventory snapshot rather than a single category list.

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 explicit guidance on when to use this tool versus alternatives such as list_site_devices, list_clients, or get_site_statistics. The description only implies an inventory use case; it does not provide when-to-use or when-not-to-use conditions.

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