fastly_list_services

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

The description discloses the read-only nature and token-scoped visibility, which is important for a tool with no annotations. It does not mention pagination, rate limits, or error semantics, leaving some behavioral details unspecified.

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 crisp sentences; the read-only hint is front-loaded, followed by the action and a forward pointer to sibling tools. No wasted words.

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 one-parameter read-only list, the description covers purpose, parameter semantics, and follow-up actions. It omits output details, but the chaining guidance suggests the returned data is compatible with fastly_list_versions or service_api_request, making it sufficiently complete for an agent to proceed.

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?

With 0% schema coverage, the description compensates by explaining the fastlyToken parameter's role ('supplied Fastly user token'). This adds meaning beyond the schema's minimal type and minLength, clarifying that the token determines which services are listed.

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 a clear verb (list) and resource (services) and specifies the scope ('visible to the supplied Fastly user token'). It differentiates from siblings by focusing on token-based listing, though it does not explicitly name alternatives.

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 offers explicit follow-up guidance ('Follow with fastly_list_versions or service_api_request'), which implies when to use this tool as an initial discovery step. It lacks explicit exclusions, but the contextual cue is useful.

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