api_get

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

With no annotations, the description carries the full burden and does the most important part: it declares the read-only guarantee ('this server can never write') and the GET-only constraint, which is exactly the safety profile an agent needs. It omits secondary traits such as auth requirements, rate limits, and how pagination or errors surface, so it is strong but not exhaustive.

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?

Two tight sentences, zero filler, with the read-only guarantee and the GET-only restriction front-loaded before the examples. Every clause 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?

There is no output schema, so the description would ideally say something about the response shape (raw API payload) or pagination conventions, and it does not. For a passthrough tool the essential calling information is present, but the return-side behavior is left unspecified.

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 'path' and 'query' are already documented in the schema. The description's path examples ('/labels', '/warehouses') largely duplicate what the schema already shows, and it adds no new syntax or format detail beyond 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?

States a specific verb ('issue an arbitrary GET') and resource ('any Segment Public API path'), with concrete path examples. It is clearly distinguishable from the sibling list_*/get_* tools, which each target a named resource, by positioning itself as the generic escape hatch.

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 'escape hatch' framing plus 'only GET is supported' tells the agent this is the fallback for endpoints not covered by the dedicated sibling tools, and that write operations are out of scope. It stops short of explicitly naming the siblings or stating a 'prefer X when available' rule, so the routing guidance is clear but not fully spelled out.

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