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. 'Delete a contact' implies a destructive, irreversible mutation, but it fails to specify critical details: whether it requires specific permissions, what happens to associated data, if deletion is permanent, or what the response looks like (e.g., success/failure confirmation). For a destructive tool with zero annotation coverage, this is a significant gap.

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, direct sentence with zero wasted words—'Delete a contact' is front-loaded and efficiently conveys the core action. Every word earns its place, making it easy for an agent to parse quickly without unnecessary elaboration.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks essential context: behavioral risks (e.g., irreversibility), permission requirements, error handling, or output expectations. The 100% schema coverage helps with parameters, but overall completeness is inadequate for safe and 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?

The input schema has 100% description coverage (the 'id' parameter is documented as 'Contact ID'), so the schema does the heavy lifting. The description adds no additional meaning about parameters beyond implying deletion requires an ID. This meets the baseline of 3 for high schema coverage, but doesn't enhance understanding (e.g., format constraints or examples).

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 'Delete a contact' clearly states the action (delete) and resource (contact), making the purpose immediately understandable. It distinguishes from sibling tools like 'get_contact_by_id' or 'update_contact' by specifying the destructive operation. However, it doesn't explicitly differentiate from other delete operations (e.g., 'delete_customer'), which slightly reduces specificity.

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. It doesn't mention prerequisites (e.g., needing a contact ID), exclusions (e.g., irreversible nature), or comparisons to other tools like 'update_contact' for modifications. This leaves the agent with minimal context for decision-making.

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