get_connector_metadata

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation through 'Get' and 'discover', but it does not explicitly state that no resources are modified, mention authentication requirements, or describe response structure. The description adds minimal behavioral context beyond what the name and verb already suggest.

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 exactly two sentences, front-loaded with the core action and resource, followed immediately by a practical usage hint. Every sentence earns its place with no filler or redundancy.

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 simple single-parameter metadata tool, the description provides enough context to invoke correctly: it explains the purpose, how to use it to discover supported connector types, and implicitly the 'service' filter behavior. There is no output schema, but the return type ('configuration schemas') is reasonably implied. It lacks explicit examples or shape details, but those are not essential for this level of complexity.

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 coverage is 100%: the single optional 'service' parameter is fully described in the schema. The tool description adds context about 'configuration schemas' and 'what config each requires', aligning with the parameter's purpose, but it does not introduce new syntax or details beyond the schema. This meets the baseline for full schema 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 uses a specific verb 'Get' with a clear resource: 'available connector types and their configuration schemas'. It clearly differentiates this metadata-discovery tool from sibling tools like get_connection_details or list_connections, which operate on specific connections rather than catalog-level metadata.

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 second sentence provides explicit usage context: 'Use this to discover what connectors Fivetran supports and what config each requires.' It doesn't state explicit exclusions or name alternatives, but the context is clear enough for an agent to know when to select this tool over connection-specific tools.

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