wikijs_detect_context

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

With no annotations, the description carries the full burden of explaining behavioral traits. It does not disclose whether detection is read-only, whether it requires an existing repository/workspace, what it does when context is absent, or what the returned context looks like. The word 'auto-detect' implies passive analysis, but important behavior remains unspecified.

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?

One sentence, no filler, and the core action is front-loaded. It is appropriately concise for a simple optional-directory tool, even though the content is somewhat underwhelming in depth.

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 definition does not explain what 'context' means or what the tool returns, and there is no output schema to fill that gap. Given siblings like wikijs_get_context and wikijs_set_context_mode, more context about the detection result and its consumability would be necessary for an agent to reliably use this tool.

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 schema description covers 100% of the single parameter, so the baseline is 3. The tool description adds 'current directory' as the default scope, but it corresponds directly to the schema's 'defaults to current' and adds no further semantic detail.

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 a clear action ('auto-detect') and a specific resource ('repository and workspace context') scoped to a directory. It distinguishes itself as a detection tool from sibling tools like get_context or set_context_mode, though it doesn't explicitly contrast with them.

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 phrase 'for current directory' gives some context, but there is no guidance on when to choose this over wikijs_get_context, wikijs_set_context_mode, wikijs_init_repository, or wikijs_init_workspace. No when-to-use or when-not-to-use conditions are provided.

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