site_info

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

No annotations are provided, so the description carries the behavioral burden alone. It discloses the returned fields (name, userid, available functions), which is helpful, but says nothing about permissions required, whether it is a safe read, or what happens with token scopes. Those omissions matter for a tool with zero structured behavioral metadata.

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 compact sentence that front-loads the primary purpose and then parenthesizes the returned fields. Every clause carries information and there is 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?

With no output schema, the description must convey return values, and it does so only for the user portion while leaving 'site info' entirely unspecified. It is adequate to identify the tool, but an agent cannot predict the full response shape or error behavior from this text.

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?

The tool takes no parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly does not invent parameter guidance for a zero-argument call.

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 names the resource precisely — Moodle site info plus the logged-in user — and enumerates the identity fields returned (name, userid, available web-service functions). It does not contrast with siblings like list_courses or course_contents, but the subject matter is distinct enough that confusion is unlikely.

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?

There is no explicit when-to-use statement or list of alternatives. Usage is only implied: the mention of the logged-in user and available web-service functions suggests it is the natural first call to identify the caller or discover which Moodle functions are enabled. An agent can infer that but must do the work itself.

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