Amazing Marvin MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the tool provides 'overview and productivity insights,' it doesn't describe what data is returned, whether it's real-time or historical, if there are rate limits, authentication requirements, or any side effects. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 well-structured and concise, with three sentences that each serve a clear purpose: stating the tool's function, when to use it, and alternatives. There is no wasted text, and information is front-loaded appropriately.

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 the tool's complexity (simple parameter, output schema exists), the description covers purpose and usage well but lacks behavioral details. With no annotations and minimal parameter info, it relies heavily on the output schema for return values. It's adequate for basic use but incomplete for full transparency, especially around what 'overview and insights' entail.

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 1 parameter with 0% description coverage (parameter 'debug' has no schema description). The tool description provides no information about parameters, not explaining what 'debug' does or its effect. However, with only 1 parameter and an output schema present, the baseline is 3 as the schema provides some structure, but the description adds no parameter semantics.

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's purpose: 'Get time tracking overview and productivity insights.' It specifies the verb ('Get') and resource ('time tracking overview and productivity insights'), making the function unambiguous. However, it doesn't explicitly differentiate from all siblings like 'get_productivity_summary_for_time_range' or 'get_daily_productivity_overview' beyond mentioning one alternative.

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 explicit usage guidance: 'Use when you need to check current time tracking status and get productivity metrics.' It also names specific alternatives for different operations: 'For starting/stopping tracking, use start_time_tracking() or stop_time_tracking(). For daily productivity overview, use get_daily_productivity_overview().' This clearly defines when to use this tool versus others.

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