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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data-coverage start date (12/2014), the linkage to register data, and the explicit limitation that only Commission meetings are included while Parliament/Council publish separately or with gaps. It does not discuss result ordering for non-default queries, which keeps this below a 5.

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?

The description is front-loaded with the core purpose, then proceeds in a predictable order: default behavior, org, body, sibling comparison, scope limit. It is dense but every element carries information; only the trailing bracketed note about sourcing original official data is somewhat boilerplate and could be dropped without loss.

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 read-only, four-parameter lookup with fully documented schema and no output schema, the description covers everything an agent needs: what is returned, what the defaults are, how each key filter behaves, the data's temporal coverage, and where the tool does not apply. Nothing material is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds behavioral meaning: it explains what happens when org or body is omitted versus supplied, and how body maps to either a cabinet or a directorate-general. The limit and date_from parameters are left entirely to the schema, which is acceptable given full schema coverage.

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 (documented lobby meetings of Commission cabinets and DGs) with explicit scope and time coverage (since 12/2014), plus what it returns (meeting records linked to register data such as budget and EP passes). It also explicitly distinguishes itself from get_lobby_network (DE version) and limits itself to Commission meetings, so an agent can tell it apart from siblings without opening any 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 spells out the default behavior with no parameters (the most active organizations), the behavior with org (all meetings of that organization), and the behavior with body (all meetings of a cabinet or DG, with concrete examples). It also names the sibling alternative (get_lobby_network for DE) and states the exclusion that Parliament and Council data is separate or incomplete.

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