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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds substantive behavioral context beyond them: returned amounts carry no currency, which prevents a real misinterpretation. It stops short of describing pagination behavior, though the schema covers auto-fetching.

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 sentences, no filler. The resource and scope lead, and the currency caveat is placed where the agent will read it as an actionable instruction — every clause earns its place.

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?

No output schema exists, so the description carries the burden of return-value semantics, and it addresses the most important gotcha (currency-less amounts). Pagination defaults are handled by the schema, so nothing essential is missing, though a note on ordering/limits would close the remaining 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%, so page, category, per_page and project_id are fully documented and the enum already lists categories. The description repeats the category list without adding syntax or filtering semantics, so it earns the baseline 3, not more.

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 (List) and resource (project budget line items) and enumerates the category domain, which sharpens the scope. An agent can distinguish it immediately from get_project_budget_item (single record) and create/update/delete_project_budget_item among the siblings.

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?

Provides explicit operational guidance — call get_organization_settings for currency_code before stating an amount — which is a real usage condition tied to this tool. It does not, however, say when to prefer this list over get_project_budget_item or how it relates to list_budgets/list_project_cost_snapshots.

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