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

With no annotations, the description carries the full transparency burden. It discloses that the tool returns full markdown content or metadata depending on summary_only, and describes the report contents. It implies a read-only operation via the verb 'read' but does not explicitly state read-only, errors, or permissions. Nonetheless, it adds meaningful behavioral context beyond the bare function name.

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 concise and front-loaded. The first sentence states the core purpose, and the second paragraph adds necessary detail about return format and report content. Every sentence contributes useful information without redundancy or fluff.

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 tool with four parameters and an output schema, this description is mostly complete. It covers the report's source (Bulgarian pension fund), the identification keys, and the summary_only toggle. It lacks explicit guidance on how to discover available reports, but that is a usage guideline concern, and the tool is otherwise well-specified.

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 baseline is 3. The description adds value by explaining the overall purpose of the parameters (identifying a specific report) and the role of summary_only in controlling output type. It also describes the report's internal content, which helps an agent understand what the retrieved data will look like.

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 begins with a specific verb+resource: 'Read a specific markdown holdings report for a Bulgarian pension fund.' It clearly identifies the scope (specific manager, fund type, date) and distinguishes itself from sibling list/index tools by emphasizing 'specific' and detailing the return behavior.

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?

Usage is implied: use when you need the full markdown content or metadata for a specific holdings report. However, it does not explicitly state when to prefer this over siblings like list_holdings_reports or get_holdings_reports_index, nor does it mention alternatives or exclusions.

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