get_device

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

No annotations provided, so description carries full burden. Description implies read-only ('获取详情') but does not explicitly state safety, permissions, or side effects. Lacks disclosure of behavioral traits beyond the action.

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?

Two concise lines plus an Args section. Every sentence is meaningful with no redundancy. Front-loaded with purpose.

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?

Given single parameter, no output schema, and no annotations, the description adequately covers what the tool does and what it returns. It is complete for a simple getter tool, though could mention if it requires authentication.

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 has one parameter 'did' with 0% description coverage. Description adds 'Args: did: 设备ID', clarifying that 'did' is the device ID, which adds meaning beyond the schema's type requirement.

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?

Description clearly states '获取设备详情，包含设备规格、可用属性列表和动作列表' (Get device details, including specifications, available property list, and action list). This uses a specific verb and resource, distinguishing it from siblings like 'list_devices' which lists all devices.

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?

No explicit guidance on when to use this tool vs alternatives. However, the purpose is straightforward, and the context of siblings makes it implied that this is for a specific device's details. Missing when-not or exclusion conditions.

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