moodle_probe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'No credentials required' but does not explicitly confirm that the tool is read-only or has no side effects. The verb 'Check' implies observation, but this is not explicit enough for full transparency.

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 exceptionally concise: two sentences, front-loaded with the core purpose, and every word adds value. 'No credentials required' is a useful addition without unnecessary detail.

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 and has an output schema, so return values are covered. The description captures the essential purpose and credential requirement. It lacks explicit when-to-use guidance, but given the tool's low complexity and output schema, this is adequate.

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 has 0% description coverage, so the description must compensate. It adds meaning by clarifying that 'url' is a 'Moodle base URL' and that the 'service' relates to 'Mobile token login'. However, it does not explain parameter formats, acceptable values, or how the default service is used.

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 uses the specific verb 'Check' and clearly identifies the resource (Moodle base URL) and what is being checked (availability of Mobile token login). This distinguishes it from sibling tools like moodle_setup or moodle_courses_list, which perform different operations.

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?

Usage is implied as a preliminary connectivity/login-availability check before using other Moodle tools, but the description does not explicitly state when to use it vs. alternatives or provide exclusions. 'No credentials required' offers some context, but the guidance is not explicit.

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