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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds value beyond them by disclosing ordering (newest first), row granularity (one row per notice transaction line), returned attributes, and the per-row source credit, which tells the agent something about result provenance.

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 scope, then granularity and filtering guidance. Efficient, though the second sentence packs several distinct facts and is slightly heavy.

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 the description need not explain return values, and it still notes row shape and source credit. Coverage, ordering, filtering and the live-markets dependency are all addressed, so an agent has everything needed to call it correctly.

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 baseline is 3; the description still adds meaning by framing issuer as a filter and explaining that country selects the live market register (with get_eu_markets as the check). It adds cross-parameter context rather than merely restating the schema.

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 names a specific resource (European insider dealings / PDMR transactions under MAR article 19) and scopes it to four named national registers, which separates it cleanly from siblings like get_insider_trades, get_congress_trades and get_form144_notices. An agent can identify the tool's domain without opening the schema.

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 clear usage context: filter by issuer id, and consult get_eu_markets to see which markets are live, plus the valid country set. It stops short of explicitly stating when to prefer this over the related non-EU insider tool, so it is clear context rather than full when/when-not routing.

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