load_guideline

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful context beyond annotations: it explains that the tool returns usage instructions, coverage information, and conditions of use. It does not describe output length or whether reading is mandatory, but the output schema exists.

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 and front-loads the tool's purpose. Every sentence adds value: the first defines the guideline and its contents, and the second gives the key invocation instruction.

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 simple, parameterless, read-only guideline tool with an output schema, the description is complete enough. It tells the agent what the guideline covers and when to read it, so no further detail is needed to select and invoke it 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 tool has zero parameters, so the baseline is 4. There are no parameter semantics to clarify beyond what the empty schema already shows.

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 states a specific purpose: it loads a usage guideline for the Jグランツ tools. It enumerates what the guideline covers (searching, reading details and attachments, scope of Jグランツ, conditions of use), which clearly distinguishes it from the sibling search, detail, and attachment tools.

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 gives explicit timing guidance: 'Read it before your first search.' This tells the agent when to invoke the tool. It does not state when not to use it or describe alternatives, but there is no obvious alternative guideline tool among the siblings.

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