skool_notifications

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

With no annotations, the description bears the full burden of explaining behavior. It only mentions that it 'Tries' the Next.js route, which hints at experimental behavior but does not disclose response format, error handling, authentication needs, or how 'recent' is defined. This is significant missing 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 followed by a brief implementation note. Every word earns its place, with no fluff or repetition.

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?

The tool is simple (1 optional param, no output schema), but without annotations, the description must explain return values and behavioral limitations. It fails to describe what the response contains or any constraints, making it under-specified for an agent to fully anticipate the tool's behavior.

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?

Schema coverage for the sole parameter 'page' is 100% with a description, so the baseline is 3. The tool description adds no additional meaning beyond what the schema already provides, which is acceptable given the high coverage.

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 'Get recent notifications' with a specific verb and resource. It is easily distinguishable from sibling tools which focus on members, posts, courses, etc. The implementation note about the Next.js data route adds context without obscuring the purpose.

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 purpose statement implies usage for retrieving notifications, but there is no explicit guidance about when to prefer this tool over alternatives or any exclusions. Since no other notification tool exists among siblings, the context is clear, but the description does not explicitly confirm when to use it.

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