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

Annotations already declare this as a safe, read-only, idempotent operation, so the description does not need to repeat that. It adds useful context that approval requirements are configurable by the org admin and that business workflow approvals always apply, but it does not explain what that means operationally for listing budget line items.

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 short but front-loading is weak: the first sentence is generic boilerplate about RetailHardHat budgets records, while the actual purpose appears only in the second sentence. The approval note is relevant but somewhat detached and could be clearer.

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 list tool with an output schema, the description gives enough to understand the broad intent, but it leaves key gaps: no distinction from list_budget_line_items, no parameter detail, and no pagination or scoping context. The output schema covers return values, so that omission is acceptable.

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 0%, so the description must carry the burden of explaining the single projectId parameter. It only implies the parameter by saying 'a project's budget line items' and does not mention that projectId is required, must be a UUID, or how it scopes the results.

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 specifies the action and resource clearly: 'Read a project's budget line items.' However, it does not distinguish this tool from close siblings such as list_budget_line_items or get_budget, so an agent cannot tell from the description alone why it should choose this one.

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 only usage guidance is the vague phrase 'Use this when working with RetailHardHat budgets records in the connected organization.' There is no explicit when-to-use versus alternatives, no when-not-to-use, and no mention of sibling tools like list_budget_line_items or get_budget.

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