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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false, covering the safety profile. The description adds no new behavioral details (e.g., response format, pagination), so it provides no extra value.

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 extremely concise (4 words), which is efficient but omits essential information like what an MEP is and the verb (e.g., 'get'). It is front-loaded but under-specified.

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?

Given the read-only nature and single parameter, the description minimally meets needs but fails to mention output format (though an output schema exists), nor does it explain the entity. Complete coverage would require at least stating 'Returns details of a single MEP by ID.'

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 0%, so the description must compensate for the parameter. It only restates 'id' from the parameter name, with no format, constraints, or background. The schema example '124688' is not referenced. This is insufficient for an agent to understand the parameter.

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 'Single MEP by id.' indicates retrieval of one MEP entity, with 'MEP' assumed as Member of European Parliament. It is clear but lacks verb specification, and the acronym is not explained, relying on context from sibling tools.

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?

No guidance on when to use this tool versus its sibling 'meps' (presumably listing multiple MEPs) or other tools. There is no mention of prerequisites or context, making it hard for an agent to choose correctly.

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