transformations_read

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that this is a 4-endpoint dispatcher and how to discover endpoints, but says nothing about pagination, auth, or error behavior.

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?

Three tight sentences, no filler, with the core purpose front-loaded before the operational instructions. 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?

For a dispatcher tool with a fully documented schema and annotations covering safety, the description supplies the essential missing piece: which endpoint names exist and where to get the authoritative list. Pagination and per-endpoint argument requirements are left implicit, which is a minor gap.

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%, so the baseline is 3, but the description goes further by defining the valid domain of `name` (the four listed endpoints) and pointing to list_endpoints for discovery. It still leaves body/query/path_params usage entirely to the schema.

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+resource ('Read operations on Fivetran transformations') and enumerates the four endpoints it multiplexes, which lets an agent map an intended call to this tool without opening the schema. It does not explicitly contrast with adjacent siblings like transformation_projects_read, so it falls just short of a 5.

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?

Gives concrete operational routing: pass the endpoint name in `name`, and call list_endpoints(category='transformations') to enumerate valid endpoints. That is genuine when/how guidance, but it offers no exclusion criteria telling the agent when a sibling read tool is the better choice.

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