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

With no annotations provided, the description carries the behavioral burden and does well by stating that it will not fill gaps or create contribution records and that missing or unreadable details must be reported. It does not discuss authentication, rate limits, or malformed-input handling, but the core extraction constraints are disclosed.

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 definition is front-loaded and appropriately short, with purpose, usage, and a behavioral guardrail. It repeats the Cyprus Social Insurance statement context slightly, which keeps it from being maximally tight.

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 a simple one-parameter parsing tool with a full output schema, the description covers the essential purpose, usage context, and important non-fabrication behavior. Minor gaps around malformed input or output shape are mitigated by the output schema and simple parameter contract.

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?

The schema has 100% description coverage for the single text parameter, so the schema already explains that it expects pasted statement text. The description adds context about the domain but does not add syntax, format, or validation details beyond what the schema provides.

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 verb and resource: extracting structured contribution history from pasted Cyprus Social Insurance Services pension statement text. It also scopes the output to supported contribution years and units, and implicitly distinguishes itself from calculation tools by saying it does not fill gaps or create contribution records.

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 clearly says to use this tool on an actual pasted Cyprus Social Insurance statement, which gives useful context for when it applies. It does not explicitly name alternative sibling tools such as get_pension_reference_data or calculate_cyprus_state_pension, so the routing guidance is clear but not exhaustive.

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