load_database_context

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

With no annotations, the description carries the full behavioral burden. It mentions the conditional nature ('if available') and the optional context, but does not explicitly state that it is a non-modifying read operation or describe what happens after loading (e.g., whether it returns data or sets internal state). This is a moderate gap for a simple tool.

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 primary action and followed by value rationale. Every sentence serves a purpose: the first states what it does, the second explains when and why. No wasted words.

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 is mostly complete: it explains purpose, timing, and optionality. However, it does not specify what the tool returns or how the context is delivered (e.g., as a string, or loaded into memory), which leaves a small gap for the agent.

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 schema has zero parameters, so the baseline is 4. The description adds meaningful context about what the loaded data contains (e.g., 'database structure, business context, or personal notes'), which implicitly clarifies that the tool itself does not require inputs. There are no parameters to elaborate on.

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: 'Check for and load custom database context if available.' It uses a specific verb ('load') and resource ('database context'), and distinguishes itself from sibling tools by highlighting its role as an optional context provider that should be checked first.

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 explicitly provides usage guidance: 'Always check this first as it can significantly speed up analysis and clarify data nuances.' This tells the agent when to use the tool (before analysis) and why, while noting context is optional—so no misuse if absent.

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