getReportsList

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

No annotations are present, so the description carries the full burden. It does not disclose behavioral aspects such as idempotency, side effects, authentication requirements, or data scope (e.g., whether it lists all reports or only user-specific ones).

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 overly brief and lacks structure. It omits a purpose statement and jumps directly to parameters, which are already in the schema. Brevity here sacrifices clarity and essential 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?

As a retrieval tool with no output schema, the description should explain what data is returned (e.g., list of reports with IDs, names), pagination, or filtering behavior. None of this is provided, making it incomplete for an agent to understand the tool's full capability.

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 coverage is 100%, so the parameter descriptions are already present. The tool description lists the three boolean parameters but does not add new meaning beyond what the schema provides. It is neither helpful nor harmful, meeting the baseline.

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 does not explicitly state what the tool does; it only lists parameter names without stating that it retrieves a list of reports. The name 'getReportsList' implies the action, but the description lacks a clear verb+resource statement.

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 provided on when to use this tool versus alternatives. Many sibling tools exist (e.g., getReportData, getReportsData) with no differentiation, leaving the agent without context for selection.

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