get_device_context

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds that context is 'selected' rather than exhaustive, but does not disclose pagination behavior, open-world response characteristics, or that 'details' is always included; these are left to the schema. No contradiction with annotations.

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?

A single sentence with no filler, front-loading the action and resource before the optional context list. Every element earns its place, and the structure is immediately scannable.

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 a rich input schema, output schema, and read-only annotations, the minimal description is mostly adequate. However, for a context-aggregating tool with nested options and multiple siblings, a short usage pointer or completeness note would improve orientation; the current text omits 'details' and 'maintenanceWindows' from its enumeration.

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 100%; deviceId, include, and noteOptions are already described with enums, ranges, and defaults. The description's list of context types roughly mirrors the include enum but omits details and maintenanceWindows, so it adds little semantic value beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('Load'), names the resource ('a device'), and enumerates the context areas included (monitoring, asset, lifecycle, note, custom-property, task). This clearly differentiates it from sibling context loaders like get_organization_context and get_scheduled_task_context by naming the device 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 this tool is for retrieving a device with selected context, but it never states when to prefer it over search_devices or get_organization_context, nor does it give exclusions. Usage context is inferable from the name and resource type, but no explicit when-to-use guidance is provided.

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