get_witzense_parking_report

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention pagination, time range handling, the meaning of acc_type 'on'/'off' in relation to parking/idling, authentication, or any return characteristics. It only repeats the tool's name-level purpose.

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 single sentence is compact and front-loaded with the key action and resource, but it is under-specified for a tool with 7 parameters and no other documentation. The brevity is not earned by completeness; it reads as a placeholder rather than a deliberately concise spec.

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?

The tool has 7 parameters, no annotations, no output schema, and no parameter descriptions. The description fails to cover essential context such as how devices are selected, what acc_type on/off signifies for parking versus idling, pagination semantics, or the expected response format. It is materially incomplete for safe 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?

Schema description coverage is 0% and the description adds no parameter explanations. Seven parameters remain undocumented in both the schema and the description; acc_type, start_row, and page_size semantics are particularly unclear, leaving the agent unable to construct a valid invocation with confidence.

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 uses a specific verb ('Get') and resource ('parking or idling records'), and it clearly distinguishes this tool from sibling tools like get_witzense_trips_report or get_witzense_fence_duration_report. It states what the tool returns with direct, unambiguous wording.

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 context on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply restates the basic function without any guidance on selecting it among the many Witzense report tools.

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