hybrid_deployment_agents_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 that this is a thin dispatcher over exactly two read endpoints, which is useful context, but it says nothing about response shape or rate limits.

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 resource and scope, then the calling convention, then the discovery step. Nothing is padding.

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 read-only dispatching wrapper with no output schema, the description covers what the tool is, how to select an endpoint, and where to enumerate options. It does not explain how body/query/path_params interact with the two read endpoints, which is a minor gap given they are largely irrelevant for GETs.

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 the schema already documents all four parameters; baseline is 3. The description adds that `name` must be one of the two named endpoints sourced from list_endpoints, which is a small increment over the schema text but not new detail on body/query/path_params.

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) and resource (Fivetran hybrid deployment agents) and enumerates the exact two endpoints it dispatches to, so an agent knows what this wraps. It distinguishes itself from generic siblings by naming the resource, though it doesn't explicitly contrast with other *_read tools.

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?

Tells the agent to pass the endpoint name in `name` and to call list_endpoints(category='hybrid-deployment-agents') to discover valid values. That is a clear, actionable usage path with no ambiguity, though there is no when-not-to-use guidance.

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