Get Advanced Forecasting Rows Of A Project

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds pagination behavior (max 100 items per page, pagination metadata in response) and mentions the API endpoint. However, it does not disclose potential rate limits, authentication details, or any side effects beyond what annotations cover.

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 concise at 4 sentences, front-loads the core purpose, and includes key details like pagination and required params. Minor redundancy (pagination mentioned twice) but overall efficient.

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?

There is no output schema, so the description partially compensates by stating 'Returns a paginated JSON array of Budget records with pagination metadata.' However, it does not describe the fields of a Budget record, leaving the agent to infer structure. The endpoint and required params are clear.

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?

Input schema has 100% description coverage, so each parameter is already documented. The description reiterates required parameters and pagination meaning but adds minimal new semantic value beyond the schema. 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?

The description clearly states it fetches advanced forecasting rows (Budget records) with pagination. It identifies the verb (Get), resource (advanced forecasting rows), and scope (by company and project). However, it does not differentiate from sibling tools like list_budget_view_detail_rows, though it is distinct in name and purpose.

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 mentions required parameters and pagination control, but provides no guidance on when to use this tool versus other budget-related tools or any exclusions. It lacks explicit 'when to use' or 'when not to use' instructions.

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