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 describes the tool as providing guidelines and instructs to call it first, implying it is a safe, read-only operation. However, it does not explicitly state that it has no side effects or whether it returns static content, leaving some 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 extremely concise, consisting of two short sentences that front-load the critical instruction to call first. Every word earns its place, and there is no redundant information.

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 (no params, no output schema, no annotations), the description is sufficient for an agent to understand its purpose and priority. It does not describe the format or content of the guidelines, but for an operational-instruction tool, this is a minor gap.

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 has no parameters (0 params, 100% schema coverage), and the description correctly adds no parameter information. Per the rubric, a baseline of 4 is appropriate when there are no params and the schema is complete, so the description does not need to compensate.

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 identifies the tool as providing 'operational guidelines for the AI,' which is a specific resource distinct from sibling tools that retrieve product-related data. The verb 'get' is implicit in the tool name, and the description conveys the core purpose without ambiguity, though it does not explicitly state the action.

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 instruction 'Call first' provides explicit guidance on when to use this tool, indicating it should be invoked before other tools. This is a clear usage directive, but it does not mention any alternatives or conditions for when not to use it, which would be unnecessary given its unique role.

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