transformation_projects_read

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a real behavioral trait beyond that: this is a dispatch/proxy tool that fans out to exactly 2 endpoints selected via `name`, plus the workflow needed to enumerate them. It stops short of describing return shape or pagination.

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 tightly packed sentences with no filler; the resource scope and the two endpoints are front-loaded before the dispatch instruction and the discovery hint.

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 multiplexed read proxy with no output schema and 100% schema coverage, the description supplies the essential context: what the tool covers, the number and names of endpoints, and how to discover valid `name` values. It omits any per-endpoint description and any routing hint versus transformations_read, which are the remaining gaps.

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 every parameter is already documented, and the schema's own `name` description already points to list_endpoints. The description only restates that the endpoint name goes in `name`, adding marginal value over the structured fields, so the baseline of 3 is appropriate.

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 and resource ('Read operations on Fivetran transformation projects') and enumerates the two underlying endpoints (list_all_transformation_projects, transformation_project_details), so the agent knows the scope. It does not, however, differentiate itself from the close sibling transformations_read, which handles a different but similarly named resource.

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 a concrete discovery step: call list_endpoints(category='transformation-projects') to obtain valid `name` values, and states that the endpoint name must be passed in `name`. This is clear usage context, but there are no exclusions or guidance on when to prefer this over transformations_read or the other *_read siblings.

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