get_group_wiki_page

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

The description only indicates a read operation ('Get') but lacks detail on permissions, error handling, or effects of parameters like render_html or version. No annotations are present, so the description must carry this burden.

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 short sentence, but it is overly minimal. While front-loaded, it lacks necessary detail for a tool with four parameters and no other documentation.

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 absence of annotations, output schema, and parameter descriptions, the description fails to provide adequate context. An agent cannot determine return format, error handling, or proper parameter usage 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?

With 0% schema description coverage, the description adds no information about the parameters (group_id, slug, render_html, version). It does not explain their roles or constraints, leaving the agent to infer from names alone.

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 clearly states the verb (Get), resource (specific wiki page), and scope (for a GitLab group). Among siblings with similar functions like get_project_wiki_page, it implicitly differentiates by specifying 'group'.

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?

No guidance is provided on when to use this tool versus alternatives like list_group_wiki_pages or get_project_wiki_page. There are no prerequisites, usage contexts, or exclusions.

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