moodle_functions

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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds token-scoped permissions ('this token can call'), which is useful auth context, but omits result size, pagination, or matching behavior; with annotations doing the heavy lifting, this is adequate but not rich.

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, front-loaded with identity and followed by routing guidance; no filler. The filter example is tucked into parentheses without disrupting flow.

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 one-parameter discovery tool with no output schema, the description conveys what is returned (function names) and how to narrow results. It lacks detail on result format or pagination, but nothing essential is missing for correct invocation.

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 is 0% and the single `match` parameter has no description in the schema. The description compensates by explaining it as a filter with a concrete example, which is meaningful beyond the schema's bare title and default.

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?

States the exact resource (Moodle web-service function names available to this token) and its role as a discovery index for moodle_call. It clearly distinguishes itself from all sibling action tools by being a read-only listing rather than an action executor.

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 says to use it when no dedicated tool fits and names moodle_call as the consumer, so the agent knows when to select it over siblings. The filter example ('calendar') gives immediate operational guidance on the one parameter.

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