freshbooks_list_projects

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

The readOnlyHint annotation already indicates a safe read operation. The description adds valuable context about businessId vs accountId and the tool's behavior without an accounting account. However, it does not disclose pagination behavior, response format, or other non-obvious traits, so it partially extends beyond annotations but leaves gaps.

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 two sentences, front-loaded with the core action ('List projects for the business'), and adds a useful caveat without any fluff. Every phrase earns its place, making it concise and well-structured.

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 pagination parameters and no output schema, the description covers the essential purpose and a key behavioral nuance. However, it omits any mention of what a successful response contains (list of projects) and does not clarify pagination defaults or limits, leaving some context incomplete given no output schema.

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 description coverage is 0%, so the description must compensate for parameter meaning. It fails to mention 'page' or 'per_page' entirely; the only parameter-like reference is businessId, which is not in the schema. The description provides no semantic value for the actual parameters, leaving pagination details undocumented.

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: 'List projects for the business.' This is a specific verb+resource pair that distinguishes it from sibling tools like freshbooks_get_project (retrieve a single project) and freshbooks_create_project (create a project). The additional note about businessId reinforces the scope.

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 some usage context: 'Uses businessId (not accountId)' and 'works even when the business has no accounting account.' This implies a scenario where the tool is especially useful, but it does not explicitly compare with alternatives or state when not to use it. No exclusion or alternative tool names are mentioned, so guidance is implied rather than explicit.

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