list_devices_basic

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

With no annotations provided, the description carries the burden. It discloses that the tool returns 'basic properties only,' is 'lightweight,' and is 'Faster than list_devices().' This conveys the reduced scope and performance advantage, which are useful behavioral traits not inferable from the name alone.

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 concise, with two sentences. The first sentence delivers the core purpose and scope, and the second adds relevant detail about the content and performance. Every sentence earns its place with no redundancy.

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 simple, parameterless list tool with an output schema, the description is complete. It states what the tool does, what fields are included, and how it differs from a sibling. The presence of an output schema covers return structure, so the description needs no further elaboration.

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?

The tool has zero parameters, and the input schema is empty, so there are no parameter semantics to clarify. Per the rubric, a 0-parameter tool earns a baseline of 4, and the description adds no conflicting or unnecessary parameter information.

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 tool's function with a specific verb and resource: 'List all devices with basic properties only.' It also distinguishes itself from the sibling tool list_devices by explicitly noting that it returns a lightweight subset and is faster, making its unique role clear.

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 provides a clear context for when to use this tool: when a lightweight, fast device list is needed, explicitly comparing to list_devices(). However, it does not explicitly state when to choose the alternative (e.g., when full attributes are needed), so it falls short of full when/when-not guidance.

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