Universal Infinite Loop MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'graceful shutdown' which implies a potentially destructive operation, but doesn't clarify what gets shut down, whether it's reversible, or any rate limits or authentication requirements. This is inadequate for a tool that appears to manage system state.

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, efficient sentence that clearly states the tool's purpose. It's appropriately sized and front-loaded with the core functionality, though it could potentially benefit from more detail given the complexity implied by the tool name and parameters.

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?

For a tool with no annotations, no output schema, and parameters suggesting system management capabilities, the description is insufficient. It doesn't explain what 'context capacity' means, what happens during graceful shutdown, or what the tool returns. The agent would need to guess about important behavioral aspects.

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 input schema has 100% description coverage, providing clear documentation for all three parameters. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline expectation when schema coverage is complete.

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 the tool's purpose as monitoring context capacity and managing graceful shutdown, which is clear but somewhat vague. It specifies the verb 'monitor' and resource 'context capacity' but doesn't clearly distinguish this from sibling tools like 'agent_coordinate' or 'wave_plan', leaving ambiguity about its specific role in the system.

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 is provided on when to use this tool versus alternatives. The description mentions monitoring and shutdown management but doesn't specify prerequisites, exclusions, or how it relates to sibling tools. This leaves the agent without context for appropriate tool selection.

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