devices_list_mobile

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

No annotations are provided, so the description carries full burden. It only says 'List managed mobile devices' with no mention of pagination, filtering behavior, authentication, or risk profile. While 'list' implies a read operation, the description discloses no 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?

The description is a single short sentence, 'List managed mobile devices,' which is efficient and front-loaded. However, it borders on under-specification for a tool with two parameters, offering minimal substance beyond the name.

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 the tool's simplicity, the description is still incomplete. It lacks information about the query filter syntax, maxResults constraints, and return format. The presence of sibling tools like devices_list_chromeos suggests shared patterns, but the description doesn't leverage them or provide enough context for reliable invocation.

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 schema has two parameters (query and maxResults) with no descriptions. The tool description does not explain what 'query' does or how maxResults behaves, leaving the agent to infer from types and defaults. With 0% schema description coverage, the description should compensate but doesn't.

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 states 'List managed mobile devices' with a specific verb and resource, clearly distinguishing it from sibling devices_list_chromeos by resource type. However, it doesn't elaborate on what 'mobile' includes or provide any further distinguishing details.

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 guidance is given on when to use this tool versus alternatives like devices_list_chromeos or users_list. The description provides no use cases, prerequisites, or exclusions.

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