freshbooks_get_identity

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

The readOnlyHint annotation already indicates the tool is read-only. The description adds context about the output types (alphanumeric vs integer) and the critical behavior that using the wrong identifier yields a 404 instead of a useful error. This is valuable beyond annotations, though it could also mention pagination or response shape if applicable.

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?

Two sentences, no fluff. The first sentence states purpose and lists identifiers with their types and usages; the second is a practical warning. 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?

Given no parameters, a read-only annotation, and no output schema, the description fully covers what an agent needs to know: what is returned, the type/usage of each identifier, and a caution about swapping them. No vital context 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 input schema has zero parameters, so the description carries no parameter burden. The baseline for 0-parameter tools is 4, and the description correctly focuses on output semantics instead.

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 resolves the authenticated user and lists the exact identifiers returned (accountId, businessId, businessUuid). It distinguishes itself from sibling tools, which all operate on specific FreshBooks resources, making it unique as an identity/metadata endpoint.

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 implicit usage guidance by explaining which identifiers belong to which API areas (accounting/payments vs projects/time tracking). It doesn't explicitly say 'call this first' but strongly implies it, and the 404 warning helps avoid misusing the returned IDs in other endpoints.

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