Get global planner report

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful provenance ("Inferred from the SingleOps web app's own traffic") and lists returned keys, but it does not explain report behavior, filtering semantics, or pagination beyond repeating parameter names.

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 opening sentence is concise and front-loaded, but the description then dumps a massive redundant list of fifty-plus query parameter names already present in the schema. That list is unreadable and does not earn 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?

For a complex 57-parameter endpoint with no output schema, the description does include the return keys, which is helpful. However, it does not explain the report's content, how the date filters should be used, or how the DataTables parameters interact, leaving significant gaps.

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 100%, so the baseline is 3 even though the schema descriptions are mostly tautological (e.g., "Query parameter draw"). The description merely repeats the same parameter names in a comma-separated list and adds no meaning about filters like table_filter_start/end or the DataTables-style parameters.

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 states a specific verb and resource ("Get global planner report") and names the backing endpoint (GET /reports/global_planner). It does not distinguish this report from the many sibling report tools or explain what the report contains.

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 guidance on when to use this report versus alternatives such as get_dashboard, list_widgets, or the other report tools. The only guidance-like remark is the caveat "confirm results," which is about reliability rather than tool selection.

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