reload_schema

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

No annotations exist, so the description must carry the burden. It discloses the return behavior (compact confirmation, verbose option for full response) and the core action of detecting changes, but does not specify whether the operation is idempotent, what side effects occur on existing schema, or any authorization/rate-limit concerns.

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 two sentences, front-loaded with the action, followed by the detection behavior and return format. It contains no filler and is appropriately sized for the tool's simplicity.

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 two-parameter tool with no output schema, the description covers the purpose, behavior, and return options. However, without annotations, it lacks explicit guidance on when to use this versus the schema-related sibling tools and does not disclose side effects or error conditions, leaving moderate gaps.

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?

The input schema already describes both parameters (verbose and connection_id) with 100% coverage. The description adds only a redundant hint about setting verbose=true, providing no additional semantic value beyond the schema.

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 the verb 'Reload', the resource 'schema configuration', and the source. It also specifies what it detects (new tables, columns, schema changes), which distinguishes it from read-only schema retrieval tools like get_connection_schema.

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 implies the tool should be used when you want to refresh the schema from the source after changes, but it does not explicitly state when to use it over sibling tools like get_connection_schema or update_connection_schema, nor does it provide exclusions.

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