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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds the scope note that only 'newest rows' are returned and that results carry 'source credit', but says nothing about auth, rate limits, or result truncation limits. Modest added value over 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?

Two dense sentences, front-loaded with the resource and its contents, followed by the parameter-sourcing note. Every clause carries information, though the comma-heavy enumeration of data categories is slightly packed.

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?

With an output schema present (so return shape need not be re-explained), full annotation coverage, and complete parameter descriptions, the description supplies the missing pieces: what the tool bundles and where the id comes from. Only the absence of explicit when-to-use routing and operational limits keeps it from being fully complete.

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 both the issuer id format (lei:/isin:/co:/name:hash) and the country market codes, making 3 the baseline. The description goes beyond that by telling the agent where to source a valid issuer id (from any get_eu_* row's issuer.id) and restates the four market codes, which is useful provenance information the schema does not supply.

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 a specific resource ('One European issuer in one market') and enumerates exactly what it returns: identity fields plus the newest rows of insider dealings, major holdings, net short positions and annual reports. This implicitly distinguishes it from the per-category siblings (get_eu_insider_dealings, get_eu_major_holdings, etc.) by framing it as a single-issuer bundle, though it never names a sibling explicitly.

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?

It gives a workflow hint ('Takes the issuer id from any get_eu_* row (issuer.id)') that helps an agent chain calls, but never states when to prefer this aggregate tool over the dedicated per-category tools or get_eu_markets. Usage is implied rather than prescribed.

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