external_secrets_managers_read

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

No annotations are provided, so the description carries the burden. It clarifies that the tool is a multi-endpoint read wrapper and that the endpoint name must be passed via `name`. It does not mention response formats, error behavior, authorization requirements, or potential side effects, though 'read' implies safety.

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 two sentences, front-loaded with the core purpose and endpoint list, and contains no filler or repetition. Every sentence contributes to understanding or usage.

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?

The tool is a generic dispatcher for three read endpoints with no output schema and no annotations. The description gives the endpoint list and points to list_endpoints for more, but does not explain what each operation returns or how to construct path_params/query for specific endpoints, leaving a moderate 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?

Input schema coverage is 100%, so the baseline is 3. The description adds minimal extra parameter meaning beyond restating that `name` selects the endpoint, which is already documented in 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?

The description clearly states 'Read operations on Fivetran external secrets managers' and lists the three supported endpoints (get_esm_details, get_esm_entities, list_esms), making the tool's purpose explicit and distinguishing it from other resource-specific 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?

The description advises calling list_endpoints(category='external-secrets-managers') for the full endpoint list, which is useful. However, it does not explicitly explain when to choose this tool over sibling alternatives like external_secrets_managers_entities_read, nor how to select among the three endpoints.

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