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. 'Create a new contact' implies a write/mutation operation, but there's no information about permissions required, whether the operation is idempotent, what happens on duplicate data, what the response contains, or any error conditions. For a creation tool with zero annotation coverage, this is inadequate.

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 maximally concise - a single three-word phrase that communicates the core function without any wasted words. It's appropriately sized for such a basic operation and gets straight to the point.

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 creation tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'contact' represents in this system, what happens after creation, whether there are validation rules, or how this entity relates to others in the system (like customers or users). The context signals indicate significant complexity that the description doesn't address.

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 no parameter information beyond what's already in the schema. However, with 100% schema description coverage, all 7 parameters are well-documented in the schema itself. The baseline score of 3 reflects that the schema does the heavy lifting, though the description adds no additional context about parameter relationships or usage patterns.

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 contact' clearly states the verb and resource, making the basic purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'create_customer' or 'create_user' - all appear to create different entity types, but the description provides no context about what distinguishes a 'contact' from these other entities.

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. With sibling tools like 'create_customer', 'create_user', and 'update_contact' available, there's no indication of when a contact should be created versus these other entities, or when to create versus update an existing contact.

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