freshbooks_get_item

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

The readOnlyHint annotation already establishes that this operation has no side effects, and the word 'Get' is consistent with that. The description adds no extra behavioral context such as error behavior or authentication requirements, though for a trivial single-item read this is only a minor gap.

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 entire description is one compact sentence with no filler. Every phrase ('single', 'numeric', 'FreshBooks id') earns its place by carrying identifying information.

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?

For a one-parameter read-only get operation, the description is complete: it identifies the resource, the required input, and the result. No output schema exists, but 'Get a single item' sufficiently conveys the return value, and nothing needed to call it correctly is omitted.

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 schema already documents the only parameter ('id') as a positive integer. The description's 'numeric FreshBooks id' merely restates the schema's type and purpose rather than adding new meaning, which matches the baseline for high schema coverage.

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 names a specific verb ('Get'), a specific resource ('a single item'), and the identifying key ('numeric FreshBooks id'), which is enough to distinguish it from sibling freshbooks_list_items. It is unambiguous and action-oriented.

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 usage is implied rather than stated: an agent can infer to use this when it has an item id and needs one item, but the description gives no explicit when-to-use guidance or alternatives such as freshbooks_list_items for retrieving multiple items. There is no exclusionary context.

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