cc_reload_tool

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

Without annotations, description carries full behavioral burden. Only states 'reload' but does not disclose side effects on active calls, concurrency safety, or whether it's safe to run repeatedly.

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?

A single, front-loaded sentence conveying the core action efficiently. Could be more informative without losing conciseness.

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?

Adequate for a zero-parameter tool with output schema, but lacks details on return value, side effects, or relation to other call center tools (e.g., cc_agent_login).

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?

No parameters exist, so description need not add param info. Baseline 4 is appropriate since schema coverage is 100% and description adds context about what is reloaded.

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) and the resource (call center agents and flows from the database), distinguishing it from sibling reload tools like carrierroute_reload or dialplan_reload.

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?

Usage is implied (reload after DB changes), but no explicit guidance on when to use versus alternatives or prerequisites (e.g., agent login state).

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