get_income_attachment

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe, read-only behavior. The description adds that the result is Base64, which is a behavioral trait, but lacks details on error handling (e.g., missing attachment) or return format structure.

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 very concise, using only a few words. It is front-loaded with the key information (attachment in Base64). However, it could be slightly more structured without losing conciseness.

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?

The description is minimal and covers the basic purpose, but with an output schema present, more details about return values are not strictly necessary. However, given the simplicity of the tool, it is adequate but not complete (e.g., no mention of behavior when income_id does not exist).

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 input schema has one parameter (income_id) with no description (0% coverage). The tool description does not mention income_id or its purpose, so it adds no value beyond the schema. Given low coverage, the description should compensate but fails to do so.

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 it retrieves an attachment of an income in Base64 format, specifying the verb (get) and resource (attachment). It distinguishes from sibling tools like delete_income_attachment and get_expense_attachment, though it could be more explicit about the operation being a retrieval.

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 alternatives (e.g., get_income, delete_income_attachment). The description does not specify prerequisites or contexts where this tool is preferred.

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