reload_connection_schema_config

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

With no annotations, description discloses it is a write operation, warns of long execution time dependent on schema size, and describes response content. Could mention if it destroys existing data but is sufficient for behavioral awareness.

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?

Well-structured: warning, purpose, note on time, response content. Every sentence adds necessary information without 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?

Covers purpose, usage prerequisites, behavioral notes, and response details despite no output schema. Provides a tutorial link for further context.

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?

High schema coverage (100%) gives baseline 3, but description adds value by explaining schema_file must be read first and request_body refers to that file, exceeding basic schema descriptions.

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?

Description explicitly states 'Reloads the connection schema config' with a specific verb and resource, and distinguishes from siblings like modify_connection_schema_config by highlighting it is a reload operation.

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?

Includes a warning to confirm with user before calling and notes potential long execution time. Lacks explicit when-not-to-use or alternatives but provides clear context for invocation.

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