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

No annotations are present, so the description carries the disclosure burden. 'Fetch' reasonably signals a non-mutating read operation, and 'inbound' adds source context, but pagination behavior, authentication needs, output format, or any side-effect caveats are not mentioned.

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 clear sentence that states the resource, scope, and source with no filler. It is front-loaded and easy to parse quickly.

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?

While the tool is simple and has only one optional parameter, the description does not provide enough context to reliably distinguish it from closely related sibling getters. There is no output schema and no guidance on what the returned requests look like, which leaves an agent guessing at the exact behavior.

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 single parameter 'status' is already fully documented in the schema with an example, and schema description coverage is 100%. The description adds no additional meaning about the parameter, so the baseline score of 3 is appropriate.

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 a specific verb ('Fetch') with a clear resource ('inbound quote and service requests from Jobber'), so an agent can tell it operates on Jobber request records. It does not explicitly differentiate itself from closely related siblings like jobber_get_quotes or jobber_get_jobs, which keeps it from a 5.

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?

There is no guidance about when to use this tool versus alternatives such as jobber_get_quotes, jobber_get_jobs, or jobber_get_invoices. The only hint is the word 'requests' in the tool name; no conditions, exclusions, or alternative routes are provided.

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