list_analytics_report_segments

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

With no annotations, the description carries the full burden, but it only adds the fact that results include download URLs. It says nothing about read-only nature beyond the verb choice, pagination behavior, or permission requirements for a tool with a limit-capped result set.

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?

A single compact sentence with the key clarification front-loaded in parentheses. No waste, though it is arguably too terse to carry the behavioral load required without annotations.

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?

There is no output schema, and the description gives only a partial picture of returns ('contains download URLs') without describing segment fields, ordering, or pagination. Adequate to select the tool but thin for calling it confidently against a chain of analytics-report siblings.

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 both instanceId and limit are already documented (including default and max). The description adds no syntax, format, or meaning beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb ('Get') and resource ('segments of an analytics report instance'), and the parenthetical disambiguates it from the sibling download_analytics_report_segment by clarifying this only lists segments and their URLs. It does not explicitly name the parent/child siblings, but the resource is concrete enough for an agent to select it.

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 '(contains download URLs)' note implies the follow-up workflow with download_analytics_report_segment, but there is no explicit when-to-use statement, no exclusion, and no mention of the sibling alternative. Usage is only implied.

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