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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value by disclosing the capability boundary that page read/edit is unavailable in this server. It still does not describe result shape or pagination behavior, but with annotations covering the safety profile that is acceptable.

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 brief sentences with the primary action front-loaded and the capability disclaimer second; no filler. Minor deduction for awkward line-wrapping/indentation artifacts in the raw text.

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 (one required param), annotations cover read semantics, and an output schema exists to carry return values, so the description need not explain outputs. The only residual gap is that 'Wiki activities' is never concretely defined for the agent.

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?

Only one parameter, and schema description coverage is 100% ('One or more course ids to list wikis for'). The description's 'across one or more courses' merely reinforces the multi-value nature already documented in the schema, adding no new syntax or constraints.

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 and resource ('List Wiki activities') plus the scope ('across one or more courses'), so an agent can distinguish it from get_course_contents or list_forums. It stops short of explicitly naming a sibling alternative, and 'activities' is slightly ambiguous (wiki instances vs. page activity), which keeps it below a 5.

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 description gives a when-not boundary ('Reading/editing pages is not supported by this server -- this tool is read-only coverage only'), which usefully rules out page-content workflows. However, it never says when to prefer this over list_courses/get_course_contents for course content discovery, leaving the selection reasoning implied.

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