RescueTime 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. While it mentions what the tool does ('Shows when during the day you were most/least productive'), it doesn't disclose important behavioral traits like whether this is a read-only operation, what authentication is required, rate limits, data freshness, or what happens with invalid date inputs. The description adds some context about the tool's purpose but lacks operational transparency.

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 perfectly structured and concise. It begins with the core purpose, provides parameter details in a clear 'Args:' section, then explains the value and use cases. Every sentence earns its place: the first states what it does, the second explains the parameter, the third describes the output insight, and the fourth explains practical applications. No wasted words, front-loaded with essential information.

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 moderate complexity (single parameter, productivity analysis), the description is reasonably complete. The presence of an output schema means the description doesn't need to explain return values. The description covers purpose, parameter semantics, and use cases adequately. However, for a tool with no annotations, it could benefit from more behavioral context about how the productivity metrics are calculated or what data sources are used.

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 description provides excellent parameter semantics despite 0% schema description coverage. It clearly explains the 'date_str' parameter with specific format details: "'today', 'yesterday', or 'YYYY-MM-DD'" and includes a default value. This fully compensates for the lack of schema descriptions. Since there's only one parameter, the description provides complete semantic understanding beyond what the bare schema offers.

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 productivity breakdown by hour' with the specific verb 'Get' and resource 'productivity breakdown by hour'. It distinguishes itself from siblings like 'get_today_summary' by focusing on hourly granularity rather than daily summaries. However, it doesn't explicitly differentiate from 'get_activity_data' or 'get_category_breakdown' which might also provide productivity-related data.

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 implied usage context: 'Useful for identifying peak productivity hours and scheduling deep work' suggests when this tool is appropriate. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_productivity_trend' (which might show trends over time) or 'get_category_breakdown' (which might categorize productivity differently). No explicit exclusions or prerequisites are mentioned.

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