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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds value beyond them: it states the operation reaches no client so no confirmation is needed, that archive_job reverses it, and that a Cotlet API key with app access is required.

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 content is useful but the opening is repetitive: 'Create a job for an account in a pipeline' and 'Creates a job for one account in a pipeline' restate the same fact. The redundant 'TaxDome:' prefix duplicates the title rather than front-loading new information.

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 7-param create tool with no output schema and a full-coverage schema, the description covers creation, the template option, reversibility, confirmation behavior and auth. Nothing critical for correct invocation appears to be missing.

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 all seven parameters are already documented in the schema. The description enumerates stage, assignee, priority, due date and template but adds no format or default detail beyond what the schema provides; baseline 3 applies.

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 a specific verb and resource (create a job), the scope (for one account in a pipeline, in a pipeline stage), and the optional fields it can carry. It also names the sibling that reverses it (archive_job), letting an agent place it against taxdome_get_job/list_jobs/archive_job without opening a schema.

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?

Names archive_job as the one-call inverse and explains the template option that pulls tasks in with the job, giving clear context for when to reach for it. It stops short of explicit when-not-to-use conditions (e.g. bulk creation vs single-account creation), so it doesn't reach 5.

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