Vitally 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. It only states what the tool does ('get tasks') without mentioning permissions, rate limits, pagination, or what the return format looks like. For a tool with 3 parameters and no output schema, this leaves critical behavioral traits undocumented.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool, though it could be more front-loaded with key details. There's no wasted text, earning it a high score for 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?

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'tasks' are, how results are returned, or any behavioral aspects like error handling. For a data retrieval tool in a system with multiple similar tools, 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%, so the schema already documents all parameters (accountId, status, limit) with clear descriptions. The description adds no additional meaning beyond what's in the schema, such as examples of status values beyond 'open' and 'completed' or context for the limit default. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states the tool 'get tasks for an account' which provides a basic verb+resource combination, but it's vague about what 'tasks' entail and doesn't distinguish this from sibling tools like 'get_account_notes' or 'get_account_conversations'. It lacks specificity about the type of tasks or their context in the Vitally system.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'search_tools' or 'get_account_notes', there's no indication of whether this is for retrieving all tasks, filtered tasks, or how it differs from other data-fetching tools. The description offers no context or exclusions.

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