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

No annotations present, so description must convey behavioral traits. Only states it 'lists saved connectors' with no mention of pagination, rate limits, return structure, or side effects. A read operation is implied but not explicit.

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?

Single sentence with a helpful usage hint, no wasted words. Could briefly mention parameters, but remains compact and purposeful.

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?

With 3 parameters and no output schema, the description omits pagination behavior, status filtering, and output format. Guidance on sibling tools is helpful, but overall incomplete for effective 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 has 3 parameters with 0% description coverage and description adds no parameter details. Despite defaults and enums in schema, the description fails to explain parameters like page, limit, or status filter, leaving the agent uninformed about filtering and pagination.

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?

Clear verb+resource with examples (databases, APIs, file-backed sources) and distinguishes from siblings like get_connector, test_connector, browse_connector by stating its role as a precursor.

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?

Explicitly recommends using this before get_connector, test_connector, or browse_connector, providing strong usage context. Does not include when-not conditions or alternatives, but the advice is clear.

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