Visum Thinker MCP Server

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It mentions the output format (CSV) and naming convention, but doesn't disclose whether this is a read-only operation, if it requires specific permissions, potential performance impact for large exports, or error handling. The description adds some context but misses key behavioral traits.

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?

Two concise sentences with zero waste. First sentence states purpose and scope, second sentence specifies output details. The emoji is optional but doesn't harm readability. Perfectly front-loaded with essential information.

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 2-parameter tool with no annotations and no output schema, the description adequately covers what the tool does but lacks completeness. It doesn't describe return values, error conditions, or behavioral constraints. The context about excluding Network Editor and file naming is helpful but insufficient for full understanding.

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 both parameters. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., doesn't clarify 'maxRowsPerTable' behavior for partial exports). Baseline 3 is appropriate when 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 clearly states the specific action ('Export all Visum tables to CSV files'), identifies the resource ('Visum tables'), and distinguishes from siblings by specifying 'except Network Editor' and contrasting with 'project_export_visible_tables' which likely exports only visible tables. The emoji adds visual emphasis but doesn't detract from clarity.

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 implies usage context by mentioning 'except Network Editor' and the output location ('project directory'), but doesn't explicitly state when to use this vs. alternatives like 'project_export_visible_tables' or 'project_export_graphic_layout'. No guidance on prerequisites (e.g., project must be open) or exclusions is provided.

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