moodle_course

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

The readOnlyHint and destructiveHint annotations already declare this as a safe read operation, and the description's '読む' is consistent with that. However, it adds almost no behavioral detail beyond the annotations, such as result format, scope, or authentication requirements.

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 a single compact sentence with zero waste and front-loads the key action and result. It is appropriately sized for a one-parameter read-only tool.

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 the simple read-only nature, one required parameter, and absence of an output schema, the description is largely complete: it says to search by course name and read a list of materials/activities. It could optionally clarify the returned fields or matching behavior, but nothing critical is missing for 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 description coverage is 0%, so the description must carry parameter meaning. It does so for the sole required parameter by stating that the query is a course-name search, which is sufficient for correct invocation even without additional match-format details.

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 states a specific verb and resource: search by course name and read the list of materials/activities. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as moodle_activity or moodle_announcements.

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?

The phrase 'コース名で検索し' implies the tool is used for course-name lookup, but there is no explicit guidance on when to use it versus moodle_activity or other siblings, and no exclusions or prerequisites are given.

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