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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so the safety profile is covered. The description adds a non-obvious domain behavior beyond the annotations: amounts are bare numbers with no currency attached, and currency_code must be fetched separately before stating a monetary value.

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?

Two short sentences with zero waste. The core purpose is front-loaded, and the currency caveat follows immediately as a single actionable instruction.

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 one-parameter read-only getter with full annotation coverage and full schema coverage, the description supplies exactly the missing piece: the bare-number/no-currency behavior plus the sibling call needed to render an amount. Return shape is unspecified but there is no output schema, so this is a minor gap.

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 description coverage is 100% and there is a single uuid 'id' parameter already documented as 'Budget item ID'. The description adds no further syntax or format detail for the parameter, so the baseline 3 is appropriate.

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?

States a specific verb ('Get'), resource ('a single project budget item'), and identifier ('by ID'), which cleanly distinguishes it from the sibling list_project_budget_items and the write siblings create/update/delete_project_budget_item.

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?

The ID-based retrieval scope is implied by 'by ID', and the description explicitly routes the agent to get_organization_settings for currency context, which is a genuine usage instruction. However, it never states when to reach for this tool versus list_project_budget_items or update_project_budget_item, so the when-to-use guidance is only implicit.

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