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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the creation action and the 'triage/review' purpose, but does not mention permissions, side effects, response format, or any restrictions. For a mutation tool with no output schema, this is a significant gap—an agent cannot anticipate what happens after invocation or what errors might occur.

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, efficient sentence with no wasted words. It front-loads the core action and key context, making it easy to scan. Every clause adds value, so conciseness is exemplary.

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 the absence of annotations, no output schema, and the tool's complexity (8 parameters, 1 required, part of a large sibling family), the description is too sparse. It does not explain the return value, the distinction from creating a job or quote, or any post-creation behavior. An agent needs more context to correctly select and invoke this tool over its siblings.

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 100% description coverage for all 8 parameters, so the schema already provides thorough meaning. The description adds a minor hint about 'photos/images' aligning with imageUrls, but this is already documented. With high schema coverage, the baseline of 3 is appropriate; the description does not introduce additional parameter semantics.

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 action ('Create'), the resource ('inbound service request or lead inquiry'), and the context ('in Jobber for office triage/review'). It explicitly mentions attached photos/images, and the phrasing distinguishes this from sibling tools like jobber_create_job or jobber_create_client, making its purpose unmistakable.

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 implies usage context with 'inbound' and 'for office triage/review', signaling it is for new customer requests that need review rather than confirmed work. However, it does not explicitly name alternative tools or conditions when not to use it, leaving some inference to the agent. It provides clear context but lacks explicit exclusion criteria.

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