get_witzense_rfid_reports

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

With no annotations available, the description carries the full burden of explaining behavior. It does not mention side effects, permissions, rate limits, or return format, leaving the agent without critical execution context.

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 concise sentence with no redundancy, but it is so minimal that it omits essential details. It is not verbose, but it also does not efficiently pack needed 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?

Given the lack of output schema and annotations, the description fails to provide a complete picture. It does not explain the return structure, filtering options, pagination behavior, or any constraints, making it inadequate for reliable tool selection and 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 description only references account and time range, but the schema includes five other parameters (imeis, card_ids, page_no, page_size) that are left entirely undocumented, despite zero schema descriptions. The agent cannot infer their meaning or optionality from the description.

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 clearly states the action (get) and the resource (RFID reporting records), including the key scope (account and time range), which distinguishes it from sibling functions focused on devices, tracks, or other report types.

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 information on when to use this tool versus alternatives, such as criteria for filtering by IMEI or card IDs, or when pagination is needed. No comparison with sibling tools is offered.

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