metadata_connector_config

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Returns metadata' but fails to mention the required prerequisite of first reading a schema file, the read-only nature, or any other side effects. The `schema_file` parameter's requirement is a significant behavioral detail omitted from the description.

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 a single sentence, concise, and front-loaded with the core purpose. No unnecessary words.

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 has a critical prerequisite (reading a schema file) and no output schema or annotations, the description is incomplete. It does not cover the required preparatory step, nor does it describe the format or structure of the returned metadata. This lack of completeness could hinder correct tool invocation.

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%, and the description adds no additional meaning beyond what the schema already provides. The crucial instruction for `schema_file` is only in the parameter description, not in the tool description. Baseline 3 is appropriate as description provides no extra semantic value.

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?

Clearly states it returns metadata of configuration and authorization parameters for a specified connector type. The verb 'Returns' and noun phrase specify the resource and scope, distinguishing it from sibling tools like metadata_connectors which list connector types.

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?

No usage guidance is provided. The description does not mention when to use this tool vs alternatives, nor does it highlight the prerequisite step of reading the schema file before invoking the tool (critical for correct invocation). This omission could lead to incorrect usage.

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