external_secrets_managers_entities_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 discloses that it's a read operation (non-destructive) and that it requires an endpoint name, but doesn't detail response format, pagination, or error behavior. It adds some context beyond the schema but not extensive.

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 sentences, front-loaded with the purpose, and no wasted words. It efficiently conveys the essential information.

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?

Given the tool is a generic read wrapper with a single endpoint, the description is complete enough. It references list_endpoints for the full list, which is a good pattern. No output schema exists, but the description doesn't need to explain return values for a list operation.

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 parameters. The description adds the key semantic that `name` is the endpoint name and that body is for POST/PATCH (though this is a read tool, so body may be irrelevant). It doesn't add much beyond the schema, but the baseline is 3 due to high coverage.

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 it performs read operations on Fivetran external secrets managers entities, specifically listing ESM entities. It distinguishes from siblings by naming the specific endpoint (list_esm_entities) and the category, 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?

It instructs to pass the endpoint name in `name` and directs to call list_endpoints for the full list, providing clear usage context. It doesn't explicitly state when not to use it, but the guidance is sufficient for a generic read tool.

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