syncthing_pending_devices

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not explain what a 'pending device' is, what triggers pending status, or what the returned data represents.

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 words are technically concise, but this is under-specification rather than conciseness. There is no front-loaded statement of purpose and no content that earns its place because there is effectively no content.

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?

For a paginated list tool with four undocumented parameters and no output schema, the description is completely inadequate. An agent cannot tell what a pending device is or how to invoke pagination correctly.

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 4 parameters (limit, cursor, fields, instance) with 0% description coverage, so the description carries the full burden of explaining them. It explains none of them — pagination via limit/cursor, field projection, and instance selection are all left unexplained.

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 'Pending devices.' is essentially a restatement of the tool name syncthing_pending_devices. It conveys the resource and a state but no verb, no scope, and no differentiation from the many sibling device/config tools. It is tautological rather than descriptive.

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?

There is no indication of when to use this tool versus syncthing_devices, syncthing_pending_folders, or any of the ~35 siblings. No prerequisites, no exclusions, no context of any kind.

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