Set grade & subject

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

With no annotations, the description carries full burden. It reveals key behaviors: selecting which local sources load and which Firebase namespace documents/history live under. It also notes the ordering constraint. Could be improved by mentioning if previous context is overwritten or if any loading occurs immediately, but still strong.

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?

Three sentences, each adding distinct value: purpose, importance, and fallback. No unnecessary words.

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 no output schema and no annotations, the description covers the core aspects: what it sets, why it's necessary, and how to handle uncertainty. It lacks explicit details on parameter formats and exact side effects, but overall sufficient for a configuration 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?

Schema description coverage is 0%, so description must compensate. It provides examples ('ci' for grade, 'maths' for subject) and directs users to 'get_context' for valid options. However, it does not specify allowed values or format, leaving some ambiguity.

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 that the tool sets the grade and subject context. It uses specific verb 'choose' and resource 'grade and subject'. It distinguishes from sibling tool 'get_context' by directing users to call it for available options.

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?

Explicitly states 'MUST be set before any other tool', providing critical ordering guidance. Also advises to use 'get_context' and ask the user when uncertain, giving clear context-aware instruction.

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