List Manual Forecast Line Items

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

Annotations (readOnlyHint, destructiveHint) already indicate this is a safe read operation. The description adds valuable context about pagination behavior ('Use page and per_page to control pagination; the response includes pagination metadata') and return type ('paginated JSON array of Budget records'), which enhances transparency beyond annotations.

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, with only 4 sentences. It is front-loaded with the core purpose, followed by usage hints and technical details. Every sentence adds value; there is no fluff.

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 there is no output schema, the description adequately covers what is returned (paginated JSON array of Budget records with pagination metadata) and required parameters. It also references the API endpoint for further context. It could mention error handling or authentication, but for a simple read tool, it is sufficient.

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 100% description coverage, so parameters are well-documented in the schema. The description reiterates that project_id is required and mentions page/per_page for pagination, but adds no new semantics beyond what the schema already provides.

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 returns a list of Manual Forecast Line Items for a project. It specifies the verb 'Returns' and the resource 'Manual Forecast Line Items on a given project'. While it doesn't explicitly differentiate from sibling list tools, the mention of 'Budget records' and 'paginated overview' provides enough specificity.

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 description gives context on when to use the tool—'enumerate Budget records when you need a paginated overview, to find IDs, or to filter by query parameters'. However, it does not mention when not to use it or suggest alternatives, such as other list or search tools available among siblings.

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