Reload configuration

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

The description adds behavioral context beyond the annotations: it explains that the tool re-reads specific files and that this takes effect without restarting the server, clarifying the runtime side-effect. Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description is consistent with these, adding useful detail.

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, front-loaded sentence that states the action and purpose without any filler. Every word contributes meaning.

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 zero-parameter tool with no output schema, the description fully covers what the tool does, why it is used, and the specific files affected. It is complete and self-contained.

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?

There are no parameters, so the baseline for this dimension is 4. The description still adds value by naming the exact config files that will be re-read, which is more specific than an empty 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 uses the specific verb 'Re-reads' and identifies the exact resources (profile.json, campaign.json, companies.json) plus the intended outcome ('so edits take effect without restarting the server'). This clearly distinguishes the tool from all sibling tools, none of which perform configuration 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?

The description clearly implies when to use the tool: after editing config files, to apply changes without a restart. It provides clear context but does not explicitly discuss alternatives or when not to use it, which is acceptable for a simple no-parameter tool with no sibling overlap.

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