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

With no annotations provided, the description carries the transparency burden. It clearly discloses that output is 'bundled theory content, NOT interpretation of any specific simulation run,' which manages expectations about the tool's behavior. It lacks details on output format or side effects, but for a read-only conceptual explainer, this is sufficient.

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?

Two sentences, highly efficient. It front-loads the core purpose, lists supported concepts, clarifies what it does NOT do, gives explicit usage scenarios, and points to alternatives. 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 (one enum parameter, no output schema), the description fully covers purpose, scope, exclusions, and alternative tools. It is complete for an agent to select and invoke the tool correctly.

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 input schema already provides 100% coverage including an enum and detailed description for the 'concept' parameter. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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?

Description states it is a 'Definitional primer' for specific framework concepts, with a clear verb ('explains') and resource (ReliaSim's framework concepts). It explicitly differentiates from sibling sim tools by clarifying it returns theory content, not simulation interpretation, making tool selection unambiguous.

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?

Provides explicit usage context: 'Use for "what is X?" / "how does X work?" / "explain the framework" questions.' Also gives a clear exclusion and alternative: 'NOT interpretation of any specific simulation run' and 'For line-specific claims... call the sim tools instead.' This is textbook when/when-not guidance.

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