users_read

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

No annotations are provided, so the description carries the transparency burden. It explicitly states the tool is read-only, which reveals a no-modification behavior, but it does not disclose details such as pagination, return types, or any special constraints. This is adequate but shallower than the calibration examples that add richer behavioral context.

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?

The description is compact and front-loaded, using two sentences to state purpose, list endpoints, and provide invocation guidance. No fluff exists; every sentence contributes to clear tool understanding.

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 read-only tool with no output schema, the description is complete enough: it names all six endpoints, tells users how to set `name`, and points to the dynamic source for the full list. It lacks deeper per-endpoint behavior, but that is reasonably deferred to list_endpoints and schema descriptions.

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?

The input schema covers 100% of parameters, including descriptions for name, body, query, and path_params, so a baseline of 3 is appropriate. The description adds useful context about how to choose the endpoint value, but does not significantly expand on parameter formats beyond what the schema already states.

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 clearly states 'Read operations on Fivetran users' and enumerates the six specific endpoints, making the tool's action and resource unmistakable. This distinguishes it from sibling read tools by explicitly identifying the resource domain and listing available endpoints.

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 gives clear operational guidance: pass the endpoint name in `name` and call list_endpoints(category='users') for the full list. It does not explicitly contrast with sibling tools or give when-not-to-use conditions, but the context is sufficient for selecting this tool for user read operations.

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