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

Annotations only declare destructiveHint=true, so the description earns credit for disclosing the real side effect that "Workflow automations may fire" and that identity fields are validated against account configuration (a common failure mode). It still doesn't say what happens on validation failure or what the created record response contains.

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?

Dense and front-loaded: required fields first, then linking, then side effects, then endpoint. Every sentence carries information, though the parenthetical examples make a few clauses run long.

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 17-parameter create tool with a nested custom_fields object and no output schema, the description covers the required-field contract, contact linking, and the automation side effect adequately. The absence of return-value explanation is acceptable given no output schema exists.

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 coverage is 100% so the baseline is 3, but the description adds real meaning: record_type_name is clarified as a job workflow (e.g. Residential) and status_name as a status within it (e.g. Lead), and primary_contact_id is explained as the homeowner link. That resolves the ambiguity in the terse schema strings.

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?

Opens with a specific verb and resource ("Create a job (project)") and names the concrete identity fields that define the object, which cleanly separates it from jobnimbus_create_contact, create_task, and create_note. The trailing endpoint note (POST /jobs) confirms the resource unambiguously.

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?

States the three required fields and the constraint that they must match account settings, plus how to link the homeowner via primary_contact_id — enough context to attempt a correct call. It does not explicitly contrast with jobnimbus_update_job or note that jobnimbus_get_account_settings should be consulted first to discover valid workflow/status names.

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