academy_welcome

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

Annotations already indicate readOnlyHint=true, so the read-only safety is covered. The description adds behavioral context by telling the agent to read the orientation back to the user in their language and offer to start at their level, going beyond the annotation.

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 are packed with essential information: when to call, what it returns, curriculum content, and how to use the result. No wasted words; instruction is front-loaded.

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 simple nature, one optional parameter, and read-only annotation, the description fully equips an agent to invoke it appropriately. It covers purpose, content, and user-facing next step.

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 fully describes the single locale parameter with enum values and a default (en). The description only mentions 'in their language,' which adds a minor usage hint but does not substantially augment the schema's parameter documentation.

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 specifies a distinct action: always call first when a user connects or asks what this is, and it explains what it returns (orientation for StudioMeyer Academy). This clearly differentiates it from sibling academy_* tools focused on levels, lessons, playbooks, and recipes.

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?

It gives an explicit trigger condition: 'ALWAYS call this first when a user connects or asks what this is.' This provides direct instruction on when to use the tool, making the guidance unambiguous.

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