Garoon Get Bulletin Categories

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

With readOnlyHint=true, the agent already knows it's a safe read. The description adds the special parentId values (1, -1, -2) which are not fully explained by the schema, and clarifies browsing behaviorais, but it doesn't disclose pagination details or response structure. Given the annotations cover safety, the description adds useful context.

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 purpose, and each word earns its place. It efficiently communicates the core action and the critical parameter nuance without waste.

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 (3 optional parameters, output schema exists, readOnly annotation present), the description is sufficiently complete. It covers the purposechers, the special parentId values, and there is nothing critical missing for a list-retrieval tool.

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 already has 100% coverage of parameters, including the special values for parentId, so the description adds little beyond what the schema provides. The description reinforces the parentId behavior but offers no new meaning for limit or offset. Baseline 3 is appropriate.

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 action ('Get bulletin board categories') and the resource ('from Garoon'), and it distinguishes the tool from siblings by focusing on categories rather than topics or facilities. It also introduces the key parameter (parentId) for browsing sub-categories.

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 implies usage by mentioning 'browse sub-categories' and special parentId values, but it does not explicitly say when to use this tool instead of alternatives or when not to use it. However, the special values provide clear context for when to use those values.

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