provider_find_device_authorization_request

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds that identification is by user code and that the result feeds an authorization decision, but it does not say whether the POST has side effects, whether it can be safely repeated, or what it returns — noteworthy given the 'looks up' wording sits awkwardly against readOnlyHint=false.

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?

Three logical lines, but the first two are near-duplicates of each other and the third is just the HTTP path, which already appears in the annotation title 'POST /cloudapi/1.0.0/deviceLookup'. The front-loaded sentence is useful; the remainder does not earn its space.

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?

With no output schema, the description should say what a device authorization lookup returns (e.g., account/user details and pending status) so the agent knows whether it can proceed to grant or deny. It also leaves the nested 'body' wrapper unexplained. Adequate for a one-parameter lookup, but incomplete for the workflow it anchors.

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%; body.userCode is already documented as 'User code associated with device authorization requests'. The description only restates that the lookup keys on the specified user code, adding no format, source, or validation detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 gives a concrete verb and resource: it 'looks up a device authorization request' and 'looks up a service account identified by the specified user code'. The two opening lines restate the same action with slightly different framing (request vs. service account), which blurs the object, but an agent can still tell this is a device-authorization lookup. It never distinguishes itself from the closely related provider_grant_device_authorization and provider_deny_device_authorization siblings.

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?

Usage is only implied through phrases like 'for approval' and 'for processing its authorization request', suggesting the call precedes a grant/deny decision. No explicit when-to-use statement or named alternative is given, even though provider_grant_device_authorization and provider_deny_device_authorization are obvious next steps. The agent has to infer the workflow position.

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