read_iulaan_attachment

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

With no annotations provided, the description carries the full burden, but it only mentions extracting text from a file. It does not disclose whether this is a read-only operation, any required permissions, rate limits, error conditions, or limitations on file size or type variants. The lack of behavioral context is a significant gap.

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 a single concise sentence that efficiently conveys the core purpose without any redundant wording or filler. Every word adds value.

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 tool with only two parameters and no output schema, the description is too sparse. It doesn't explain what the extracted text looks like, how the output is returned, or under what circumstances this tool should be preferred over other Iulaan utilities. The agent is left with incomplete information to make effective use of the tool.

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 0% description coverage for its two parameters, and the description does not mention them at all. The 'max_chars' parameter is completely unexplained, leaving the agent without any semantic understanding of how to set it or what it controls.

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 clearly states the tool's function: extracting text from an official Iulaan PDF or DOCX attachment. This is a specific verb and resource, and it distinguishes itself from sibling tools like search_iulaan or get_iulaan, which focus on other aspects of Iulaan 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?

No guidance is provided on when to use this tool versus the sibling tools. There is no mention of alternatives, prerequisites, or exclusions. The description only states what it does, not the context in which it should be invoked.

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