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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the note that the content is 'Static text', reinforcing that nothing is computed or mutated, but says nothing about length, structure, or how the text is returned.

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 plus a two-word qualifier. The topic list is dense but each item earns its place by telling the agent what concepts are covered.

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, annotation-covered reference tool with no output schema, the description covers what content is available. The remaining gap is the return shape (single blob vs. sectioned text) and the lack of differentiation from the explain_* siblings, which matters because there is no output schema to clarify.

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 takes zero parameters, so there is no parameter meaning to convey; the baseline of 4 applies. The description correctly spends no space on nonexistent arguments.

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 names the source (SC Builder engine) and enumerates the exact content topics: event-driven model, ordering policies, forecast-demand and order-point formulas, BOM, routing and supplier selection. An agent can tell this is a documentation/reference lookup rather than a computation, though it does not explicitly distinguish itself from the explain_* siblings.

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?

There is no when-to-use guidance and no mention of alternatives, even though siblings like explain_simulation and explain_optimization plausibly overlap in intent. The only routing signal is the implicit one carried by 'Reference text' and 'Static text', leaving the agent to infer that this is for conceptual background.

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