eu-company-mcp-server

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

Discloses scope of returned data (direct vs ultimate parent, direct subsidiaries only) and valid range for limit (1-50) without contradicting annotations.

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?

Extremely concise, front-loaded with purpose, uses structured Args section efficiently with no extraneous text.

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?

Adequately describes return values (hierarchical entities) despite missing output schema; could clarify if subsidiaries are recursive or direct-only (though 'direkten' implies direct).

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?

Fully compensates for 0% schema description coverage by explaining LEI code purpose and limit constraints (max subsidiaries 1-50).

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?

Clearly states it retrieves corporate group structure (parents + subsidiaries) and distinguishes from simple company lookup siblings like company_by_lei.

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?

Implies usage by describing returned entities (direct/ultimate parents, subsidiaries) but lacks explicit when-to-use guidance versus alternatives.

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