freshbooks_get_estimate

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

The readOnlyHint annotation already establishes this as a safe read operation, and the description's 'Get' aligns with that without contradiction. The description adds little beyond that, such as error behavior or response format, but for a simple get-by-id tool the annotation coverage is sufficient.

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?

One compact sentence with no filler, placing the verb and resource first and the key selection criterion ('numeric FreshBooks id') last. Every word earns its place.

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?

With one well-documented required parameter, a readOnly annotation, and no output schema needed for a straightforward fetch, the description is sufficient for an agent to invoke the tool correctly. Nothing essential is missing.

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 single required id parameter with type, bounds, and a description. The description's 'numeric FreshBooks id' reinforces the parameter type but does not add material semantic value 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 states a specific action ('Get a single estimate') on a specific resource, qualified by 'numeric FreshBooks id'. This clearly distinguishes it from list_estimates and from state-changing siblings such as accept_estimate or update_estimate.

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 phrasing 'single estimate by numeric id' establishes a clear use case: retrieve one known estimate by its id. It does not explicitly name alternatives like list_estimates for searching, so it stops short of full alternative routing.

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