MidOS Research Protocol MCP

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

No annotations provided, so description carries full burden. It explains default behavior ('you'll get sensible defaults') but omits mutation details, idempotency guarantees, or whether this establishes persistent session state versus ephemeral configuration.

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?

Front-loaded with critical timing instruction ('Call this FIRST'). Args section is necessarily verbose given zero schema coverage, but every parameter example earns its place. Minor deduction for slightly dense formatting.

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 presence of output schema (not shown but indicated), description appropriately omits return value details. Covers onboarding purpose, sequencing, and parameter semantics comprehensively. Could improve by clarifying side effects or persistence guarantees.

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 has 0% description coverage, but description fully compensates by documenting all 7 parameters with concrete examples (e.g., 'claude-opus-4-6', '200000', 'fastapi,react') and clarifying special values ('0 = auto-detect').

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 opens with specific verb-noun pair ('agent onboarding', 'get optimal config') and explicitly distinguishes from sibling tool agent_bootstrap by stating 'Call this FIRST when connecting to MidOS', establishing clear sequencing.

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?

Provides explicit temporal guidance ('Call this FIRST') and operational instructions ('Pass as much info as you know', 'Unknown fields can be left empty'). Clearly signals this is the entry point for the session.

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