moodle_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds what is actually searched (activities, files, section text) and the default scoping to current courses, but omits result limits, pagination, or match semantics (substring vs fuzzy).

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?

A single front-loaded sentence with no filler; the scope parenthetical is the only compressed element. Every clause conveys information the agent needs.

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 read-only search tool with two parameters, this is close to adequate, but with no output schema an agent still lacks any sense of result shape, ordering, or cap. The description covers scope but not the outcome of the call.

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%, so the description must compensate: it does explain that `query` is the term to match and that `course_ids` defaults to 'current courses' when not supplied. It adds no syntax or type detail beyond that, leaving the parameter contract thin for a zero-coverage schema.

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 a specific verb ('Find') and concrete resources ('activities, files and section text') plus the search scope. It is clear enough to distinguish from content-fetching siblings like moodle_read or moodle_course_contents, though it does not name them.

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 by the phrase 'across current courses (or the given ones)', which tells the agent this is a keyword search scoped to enrollment. However, no explicit when-to-use, when-not-to-use, or named alternative (e.g. moodle_course_contents for browsing) is given.

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