eu-company-mcp-server

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

Discloses key data characteristics (monthly, seasonally adjusted) but lacks information on rate limits, caching, or error behaviors that annotations don't cover.

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 with purpose front-loaded in first sentence; Args section efficiently documents parameters without redundancy.

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?

Adequate for simple 2-parameter tool but omits return value description needed due to missing output schema; doesn't specify data source or units.

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?

Excellent compensation for 0% schema coverage by providing detailed Args section with format specifications ('Ländercodes', 'YYYY-MM') and concrete semicolon-separated 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?

Clearly states it retrieves unemployment rates ('Arbeitslosenquote') for EU countries with monthly seasonally-adjusted data, distinguishing it from siblings like eu_gdp or eu_inflation.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., eu_business_demography) or when not to use it.

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