scholarly-mode-start

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

The description discloses that the tool returns a systemPrompt for use in scholarly mode, which is the key behavioral output. Although no annotations exist, the description offers clear state information. It could be more explicit about side effects like state reset on repeated calls, but is adequate for a simple toggle.

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 two sentences, front-loaded with the action and followed by the return value. Every word earns its place; no wasted 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?

Given no parameters and no output schema, the description explains the tool's purpose and return value. It adequately covers the basic context, though mentioning that the prompt should be used as a system message would improve completeness. Overall, it is sufficient for a simple mode switch.

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 zero parameters, the baseline is 4. The description correctly reflects this by not mentioning any parameters, and schema coverage is 100%. No additional clarification is needed.

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 tool starts scholarly mode and distinguishes it from the sibling tool scholarly-mode-stop. The verb 'start' and resource 'scholarly mode' are specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives like get_articles_list or scholarly-mode-stop. It lacks context about prerequisites or conditions for starting scholarly mode.

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