freshbooks_get_project

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

Annotations already provide readOnlyHint=true, covering the read-only safety profile. The description adds no further behavioral detail such as error behavior, authentication requirements, or response shape, though the 'single project' wording does clarify cardinality.

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?

A single, front-loaded sentence conveys the operation, resource, and cardinality with no filler or redundancy. 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 one-parameter, read-only get-by-id tool with no nested objects or output schema, the description plus schema and annotations is sufficient for an agent to select and invoke it correctly. No additional context like pagination or filtering is relevant here.

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 100%, so the schema already documents id as a positive integer with the description 'Project id'. Saying 'numeric id' reinforces the type but contributes no new semantic meaning beyond the schema.

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?

States an action 'Get', a single resource 'project', and the key condition 'by its numeric id'. This clearly separates it from freshbooks_list_projects (plural/list) and other get_* tools for different resources.

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 phrase 'by its numeric id' signals that this is for retrieving one specific project when the ID is known, and the sibling tool freshbooks_list_projects provides the obvious alternative when listing is needed. It does not explicitly state exclusions, so it stops short of a 5.

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