system_keys_read

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

With no annotations, the description carries the burden of behavioral guidance. It notes the operation is 'read' and lists endpoints, but does not disclose return-value shape, auth needs, or potential error/pagination behavior. It's adequate but not rich.

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; the first states what the operation does and the intention of 'name', the second tells the user how to discover the full endpoint list. Every phrase earns its place.

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 generic read wrapper with no output schema, the description is reasonably complete. It identifies the 2 available endpoints, tells the user to pass the endpoint via 'name', and points to list_endpoints for a fuller list. Slightly more depth around when 'body' or 'query' are needed could improve yield, but overall it's sufficient.

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 parameters 'body', 'name', 'query', and 'path_params' are all described. The description adds no new parameter meaning beyond pointing out that 'name' accepts an endpoint name and may come from list_endpoints. Baseline of 3 is appropriate.

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 system keys' and names the two endpoints (get_system_key_details, get_system_keys). This makes the exact resource and action explicit, distinguishing it from sibling read tools for other Fivetran entities.

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 actionable usage guidance: pass the endpoint name in 'name' and call list_endpoints(category='system-keys') for the full list. It doesn't explicitly say when to use vs. alternatives, but there are no close alternatives for system keys.

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