freshbooks_list_estimates

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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds behavioral context by noting the return shape ("items plus page/pages/total") and the raw pass-through nature of filter params, which is valuable beyond the annotation.

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, front-loaded with the core purpose, and no wasted words. Efficiently conveys pagination, filter support, and return shape.

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 three params, no output schema, and good annotations, the description is sufficiently complete for a list operation. It mentions pagination, raw filters, and the return summary, covering key operational aspects without being verbose.

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 coverage is 100%, so the baseline is 3. The description does not add parameter details beyond what the schema already explains (e.g., search raw filter params and pagination). It reinforces the schema but does not extend it.

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 the tool's function with a specific verb and resource: "List estimates for the authenticated FreshBooks account." It distinguishes itself from sibling tools like freshbooks_get_estimate (singular) by using "list" and mentioning pagination/filters.

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 implies clear usage: use this tool to list estimates, especially when pagination or raw filters are needed. It does not explicitly mention alternatives, but the context of sibling tools (e.g., get_estimate) makes the when-to-use clear.

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