TimeChimp MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. 'Create a new project' implies a write/mutation operation but doesn't disclose permissions needed, whether creation is idempotent, what happens on failure, rate limits, or any side effects. This is inadequate for a complex creation tool.

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 extremely concise at just three words. While this represents severe under-specification, it's not verbose or poorly structured—every word directly states the tool's action. The problem is insufficiency, not lack of conciseness.

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 complex creation tool with 16 parameters, nested objects, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what a successful creation returns, error conditions, or the operational context. The agent lacks essential information to use this tool effectively.

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 description coverage is 100%, so the schema fully documents all 16 parameters. The description adds no parameter information beyond what's in the schema, meeting the baseline score of 3. However, it doesn't compensate for the schema's complexity by explaining relationships between parameters (e.g., how invoicing.method affects other fields).

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 'Create a new project' is a tautology that restates the tool name without adding specificity. It doesn't distinguish this tool from sibling creation tools (e.g., create_contact, create_customer) beyond the resource type, and lacks details about what constitutes a 'project' in this context.

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. There's no mention of prerequisites, when not to use it, or how it relates to sibling tools like update_project or delete_project. The agent receives zero contextual usage information.

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