androidapi_get_devices

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds the behavioral trait of pagination, but does not elaborate on defaults, limits, or ordering, so it adds moderate but not deep transparency.

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 sentence that efficiently conveys the tool's purpose and a key feature (paginated). It is front-loaded and contains no extraneous words. Every word earns its place.

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 no output schema and significant sibling tools, the description is too brief. It does not explain what device properties are returned, default pagination behavior, required authentication, or any filtering capabilities. The agent has insufficient context to use the tool effectively.

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?

With 0% schema description coverage, the description should compensate. The word 'paginated' hints that page and limit control pagination, but it does not explain their exact semantics, valid ranges, or defaults. This provides minimal added meaning beyond the schema's type definitions.

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 'List linked Android devices (paginated)' clearly states the verb (List), the specific resource (linked Android devices), and notes pagination. This purpose is distinct from sibling tools like androidapi_get_contacts or androidapi_get_groups, which target different resources.

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 no guidance on when to use this tool versus alternatives like androidapi_get_contacts or androidapi_get_groups. It does not specify prerequisites, context, or scenarios, leaving the agent without decision support.

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