freshbooks_get_estimate

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

The readOnlyHint annotation is true, and the description aligns with a read-only operation. The description adds no additional behavioral context beyond what the annotation provides (e.g., no mention of errors, auth, or return format). Since annotations already cover the safety profile, the bar is lower, and the description is acceptable but adds no extra transparency.

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 a single, front-loaded sentence that directly states the action and target. There is no filler or redundant phrasing; every word contributes to clarity.

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?

This is a simple getter tool with one parameter, a readOnly annotation, and no output schema. The description sufficiently communicates the operation and expected result (the estimate object). Given the low complexity and full schema coverage, no additional detail is necessary.

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 schema fully documents the only parameter 'id' with type integer and a description. The description's phrase 'numeric' merely restates the integer type and adds no new meaning. With 100% schema coverage, the baseline score of 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 uses a specific verb ('Get') and clearly identifies the resource ('single estimate') and the exact scope ('by its numeric FreshBooks id'). It effectively distinguishes this tool from sibling tools like freshbooks_list_estimates, which would retrieve multiple estimates.

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 context is clear: this tool should be used when a specific estimate is needed by its ID. While it does not explicitly name alternative tools (e.g., list_estimates), the phrase 'single estimate' implies that contrast. There are no explicit exclusions or conditions, but the intended usage is unambiguous.

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