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

There are no annotations, so the description carries the full burden of disclosure. 'Create and book' communicates that this is a mutation possibly affecting job and visit records, but it doesn't mention permissions, idempotency, whether repeated calls create duplicates, or what response the agent should expect. This is a significant transparency gap for a creation tool.

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 tight sentence with no filler, front-loading the core action and keeping optionality in a trailing clause. 'Book' and 'appointment scheduling' are mildly redundant, which keeps it from a 5.

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 10-parameter creation tool with no output schema and no annotations, one sentence is insufficient. The description doesn't clarify how the various date/time parameters interrelate, the required fields are only in the schema, and there's no mention of what the tool returns on success. The agent must rely heavily on the schema with no additional guidance.

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 baseline of 3 applies. The description adds almost no parameter-level meaning beyond stating that appointment scheduling is optional, which is already clear from the optional date/time properties in 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?

The description states a specific verb ('Create and book') and a resource ('field service job work order in Jobber'), which clearly distinguishes it from sibling tools like jobber_create_quote and jobber_create_client. The optional appointment scheduling is also mentioned, though it doesn't explicitly contrast with jobber_schedule_visit, preventing a perfect score.

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 this tool is for creating a new job, and 'optional appointment scheduling' hints at when scheduling fields should be used. However, it does not explicitly state when to use this tool versus alternatives like jobber_schedule_visit or jobber_create_quote, leaving usage guidance only implicit.

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