analytics_reports__instances__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the endpoint path but no extra behavioral context such as pagination behavior or response format. It does not contradict annotations and meets the baseline given the annotation coverage.

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 a useful endpoint reference. It is front-loaded and avoids unnecessary words or repetition.

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 is a straightforward list operation with good annotations and complete schema coverage. However, it lacks guidance on how it relates to adjacent instance/segment tools, which would make it fully complete for agent decision-making.

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%, with all five parameters described. The description does not add parameter-level meaning beyond the schema, so a baseline of 3 is appropriate. The filter descriptions are present in the schema, and the description does not need to compensate.

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 a specific action ('List') on a specific resource ('instances belonging to an analytics report'), making the tool's purpose unambiguous. The endpoint reference further clarifies scope. This distinguishes it from sibling tools like analytics_reports__get or analytics_report_instances__get.

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 related tools such as analytics_report_instances__get or analytics_report_instances__segments__list. There is no mention of prerequisites, filtering options, or alternative paths.

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