Reload Configuration

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the reload is 'hot' and reads 'from disk,' but it does not disclose side effects, prerequisites (e.g., admin permissions), error behavior, or whether the reload affects other components. This leaves significant behavioral ambiguity.

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 short sentences that get straight to the point: 'Hot-reloads the OAuth provider configuration from disk. Useful after updating scopes or provider settings.' No wasted words, and the most essential information is front-loaded.

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?

Given the tool's simplicity (zero parameters, no output schema), the description covers the core purpose and a common use case. It is missing details like error handling or preconditions (e.g., config file must exist), but for a straightforward reload action, it is reasonably complete.

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 tool has zero parameters, so the input schema is empty and there is nothing to document. The baseline for no params is 4, and the description correctly does not invent parameter details. It adds no parameter-specific meaning, but none is needed.

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 tool's function with a specific verb and resource: 'Hot-reloads the OAuth provider configuration from disk.' This unambiguously identifies what the tool does and distinguishes it from any sibling tools, none of which handle configuration.

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 provides a clear usage context: 'Useful after updating scopes or provider settings.' This tells the agent when the tool is appropriate. However, it does not explicitly mention when not to use it or alternative tools, so it loses a point for lacking exclusions or alternatives.

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