TimeChimp MCP Server

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. 'Create a new expense' implies a write/mutation operation, but it doesn't disclose critical traits such as authentication needs, rate limits, whether the creation is idempotent, what happens on failure, or the expected response format. For a mutation tool with zero annotation coverage, this is a significant gap in 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 a single, efficient sentence—'Create a new expense'—with zero wasted words. It's front-loaded and appropriately sized for its purpose, though it could benefit from more detail. Every word earns its place by stating the core action clearly.

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 complexity (10 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't explain what an 'expense' entails in this system, how it relates to other resources (e.g., customers, projects), or what the tool returns upon success. For a mutation tool with rich input schema but no output or behavioral hints, more context is needed to guide effective use.

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%, meaning all parameters are documented in the input schema with descriptions (e.g., 'date' as 'YYYY-MM-DD format', 'rate' as 'expense rate/price'). The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting, but doesn't compensate with extra context like examples or usage tips.

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 expense' clearly states the verb ('Create') and resource ('expense'), which is adequate. However, it doesn't differentiate this tool from sibling tools like 'create_mileage' or 'create_project' that also create different resource types, nor does it specify what constitutes an 'expense' in this system (e.g., a billable cost vs. mileage). This makes it vague compared to more specific alternatives.

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. For example, it doesn't mention when to choose 'create_expense' over 'create_mileage' (likely for different expense types) or 'create_project' (for project creation), nor does it indicate prerequisites like required permissions or dependencies. This lack of context leaves the agent to infer usage from tool names alone.

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