analytics_report_instances__segments__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, fully covering the safety profile. The description adds the scoping constraint 'belonging to an analytics report instance', but doesn't disclose additional behavioral traits such as pagination behavior or response specifics beyond what the schema parameters imply.

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 sentence with immediate purpose, followed by the endpoint. No filler or redundancy – every part earns 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 simple list operation with clear annotations and 100% schema parameter coverage, the description is sufficient. However, since there is no output schema and the description doesn't describe the response format or pagination behavior, it isn't fully complete.

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%, with id, limit, and next_url all described. The description adds no extra parameter meaning beyond the endpoint path, so the baseline 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?

The description states 'List the segments belonging to an analytics report instance' with a specific verb and resource, and includes the HTTP endpoint. This clearly distinguishes it from sibling tools like analytics_reports__instances__list (lists instances) and analytics_report_segments__get (gets a single segment).

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 description clearly implies when to use it: when you need the segments for a specific analytics report instance, identified by its id. It does not explicitly name alternatives or exclusions, but the context is unambiguous.

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