rm_get_report_rows

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds nothing about pagination, row limits, required report configuration, or any other behavior beyond the 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?

The description is a single short sentence with no filler or redundant text. It is front-loaded and efficient, though it sacrifices informativeness for brevity.

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 a free-form nested parameter and no parameter guidance, the description is incomplete for correct invocation. The output schema may cover return values and annotations cover safety, but the central input contract is undocumented.

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 sole parameter, report_parameters, is an open object with additionalProperties true and 0% schema description coverage. The description provides no details about what keys should be included, what formats are expected, or what 'custom report' parameters should look like, leaving an agent unable to construct a valid request.

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 names a specific deliverable, 'detailed custom report rows', and uses a verb, 'Generate', that conveys an action. It is not tautological and the 'rows' wording distinguishes it from the sibling rm_get_report_totals, though it does not explicitly explain what 'custom report' means.

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?

No guidance is given about when to use this tool versus alternatives such as rm_get_report_totals or the many list/get tools. The description implies it is for report rows, but it does not provide context, prerequisites, or exclusions.

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