study_live_courses

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

The annotations already establish openWorldHint=true, destructiveHint=false, and readOnlyHint=false, and the description adds useful operational context beyond them: persistent campus session, no host browser, bounded pagination, evidence recording, and job_id return. It does not contradict the annotations, though it does not cover rate limits or auth requirements in depth.

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 front-loaded with the core action and delivery mechanism, then quickly covers pagination, return value, polling, and login fallback. Every sentence adds operational value with no filler.

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 job-starting tool with no output schema, the description usefully explains the job_id return and polling follow-up. However, with 0% schema description coverage, it should explain what the query and max_pages parameters control, and it does not.

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% for two parameters. The description never mentions 'query' and only hints at 'max_pages' through the phrase 'bounded pagination,' leaving both parameters largely unexplained.

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 gives a specific verb and resource: 'Refresh Learn courses' through the plugin's own persistent campus session. It is clear what the tool does, but it does not explicitly distinguish itself from sibling live tools such as study_live_resources or study_live_myed.

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 provides concrete follow-up guidance: 'poll study_school_job' and 'On needs_login use study_connect_school.' This tells the agent what to do after invocation and on a common failure path, though it does not give explicit when-not-to-use guidance versus sibling tools.

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