teams_read

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that this is a dispatcher requiring an endpoint name sourced from list_endpoints, but says nothing about auth requirements, pagination, or per-endpoint prerequisites (e.g. path_params for membership lookups).

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 short sentences, front-loaded with the scope and endpoint inventory, followed by the two invocation facts an agent needs. Every sentence earns its place with no restatement of the name or annotations.

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 multi-endpoint dispatcher with no output schema, the description supplies the endpoint inventory and the discovery path, which is the core of what an agent needs. It leaves per-endpoint parameter requirements and response shape unstated, which is a modest but real 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 beyond the generic schema text by enumerating the valid values for `name` and pointing at list_endpoints as the authority for that value set. It still does not explain which endpoints require path_params or query, leaving the nested-object parameters 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 (read operations) and resource (Fivetran teams), and enumerates the eight concrete endpoints reachable through the dispatcher, so the agent knows exactly what is behind the name. It distinguishes itself from siblings only implicitly by resource scope; there is no explicit contrast with users_read or groups_read, which would be needed for 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 clear operating instructions: pass the endpoint name in `name` and call list_endpoints(category='teams') for the full list. This is actionable context without exclusions, but it does not say when a caller should prefer a different *_read sibling over this one.

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