freshbooks_list_services

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

The readOnlyHint annotation already discloses that this is a safe read-only operation. The description adds no further behavioral details such as pagination behavior or return format, but it does not contradict the annotation either. Minimal viable transparency given 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?

The description is a single concise sentence with an effective parenthetical clarification. It is front-loaded, contains no filler, and 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?

For a simple list tool with no output schema and only optional pagination parameters, the description sufficiently defines the resource and its domain. A minor gap is the absence of pagination defaults or response format, but the simplicity and read-only annotation keep this from being a major deficiency.

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?

With 0% schema description coverage, the description should compensate for parameter understanding, but it says nothing about page or per_page. Although these parameter names are self-explanatory, the description adds no meaning beyond the schema's basic type/range constraints.

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 the specific verb 'List' with the resource 'services' and adds clarifying context that services are 'billable work types available to projects and time entries.' This clearly distinguishes it from sibling tools like freshbooks_list_projects or freshbooks_list_items.

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 provides useful context about what services are and where they are used, helping an agent infer when to use this tool. However, it does not explicitly mention alternative tools or exclusionary conditions, so it stops short of a full when/when-not guide.

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