wikijs_get_context

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

There are no annotations, so the description carries the full behavioral burden. It only adds that the information is 'current' and 'optimized for Claude consumption,' with no disclosure of side effects, state dependencies, or return characteristics.

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 front-loaded sentence with no filler. The 'optimized for Claude consumption' qualifier hints at output format, though it is somewhat vague and does not earn full marks.

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 and no annotations, the description should clarify what 'context information' includes and how mode affects the result. It leaves the response shape and the relationship to context-detection or status tools unexplained, though the simple one-parameter schema limits the gap.

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 100%: the single optional mode parameter is fully enumerated with a meaningful description saying it uses the current mode by default. The tool description adds no additional meaning to the parameter, so the baseline 3 is appropriate.

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 clear action ('Get') and resource ('current context information'), so the agent recognizes it as a read-style retrieval. However, it does not distinguish this tool from siblings like wikijs_detect_context or wikijs_set_context_mode, and 'context' remains undefined.

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 when-to-use guidance is provided. The description never contrasts this tool with wikijs_detect_context, repository_status, workspace_status, or set_context_mode, so the agent must infer selection from the name alone.

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