get_hwid_devices

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful non-obvious behavior: filters rely on expensive LIKE operators and misuse can degrade database performance, which is not derivable from the schema or 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?

Brief and front-loaded: the purpose line comes first, followed by a single targeted warning. No padding or repetition, though the first line is essentially a restatement of the tool name rather than added information.

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 6 parameters, nested filter/sort structures, 33% schema coverage, and no output schema, the description should explain how to construct filters and sorting. Instead it only warns about performance, leaving the agent without enough information to invoke the tool correctly with filters.

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 only 33% across 6 parameters, including nested 'filters' and 'sorting' objects whose item fields are undocumented. The description acknowledges that filters exist but adds no detail on valid filter ids, values, sorting syntax, or filter modes, so it fails to compensate for the schema gap.

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?

States a clear verb+resource ('Get HWID devices') and includes the underlying endpoint, so the operation is identifiable. However, it gives no differentiation from close siblings like get_user_hwid_devices, get_hwid_devices_stats, or get_top_users_by_hwid_devices, leaving ambiguity about which HWID-device view this returns.

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 warns that filters are primarily for frontend use and can be expensive, which implies a usage constraint. But it never says when to choose this tool over get_user_hwid_devices or the stats variants, and no prerequisites or exclusions are stated.

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