get_income

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds that it returns 'complete detail', implying a full record rather than a summary. This adds some context beyond annotations, but does not disclose other behavior like response format or access control.

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 quickly conveys the tool's purpose. It is front-loaded and efficient, with no unnecessary words. However, it could marginally improve by including the parameter context.

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 low complexity (single parameter, output schema exists), the description is adequate but minimal. It states the purpose but omits details like how to identify the income (via income_id) or what 'complete detail' entails. With an output schema present, the return values are covered, but the description could still be more informative.

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 description coverage is 0%, meaning the parameter income_id has no description in the schema. The tool description does not compensate; it does not mention the parameter at all. The agent receives no additional meaning about the parameter beyond it being an integer and required.

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 'Complete detail of an income' clearly indicates a retrieval operation for a single income record. It distinguishes from sibling tools like list_income (listing) and delete_income (deletion) through the verb 'get' and the resource 'income'. However, it does not explicitly say 'get' or 'retrieve', but it is implied.

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 given on when to use this tool versus alternatives like list_income or get_income_attachment. There is no mention of when it is appropriate (e.g., to fetch a single record by ID) or when not to use it. The agent is left to infer from the tool name and parameters.

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