edit_project_wiki_page

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

Only implies mutation via 'Edit'. No annotations provided, but description does not disclose error handling, permissions, or effects on other operations. Minimal beyond the tool name.

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?

Single sentence, no waste. However, lacks structure (e.g., no bullet points or parameter explanations). Could be more informative while remaining concise.

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 5 undocumented parameters and no annotations or output schema, the description is far from complete. Does not help an agent understand required inputs or expected behavior.

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%, yet description adds no meaning to parameters like project_id, slug, title, content, or format. Enum for format is not mentioned.

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?

Description clearly states verb 'Edit' and resource 'existing wiki page for a GitLab project', distinguishing from siblings like create_project_wiki_page, delete_project_wiki_page, get_project_wiki_page, and edit_group_wiki_page.

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 on when to use vs alternatives such as create_project_wiki_page or edit_group_wiki_page. No prerequisites or context provided.

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