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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds real context: the returned content (pipelines, ordered stages, job templates) and an auth prerequisite (Cotlet API key with access to this app). It stops short of pagination or list-completeness details.

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?

Three front-loaded sentences that each carry information (purpose, routing, auth). Minor redundancy: the opening fragment 'Pipelines with their stages and job templates' restates what the next sentence already says, and the 'TaxDome:' prefix duplicates the title.

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 zero-parameter, read-only list tool with annotations covering the safety profile and no output schema, the description supplies everything needed: what is returned, the ordering of stages, the downstream use, and the auth requirement.

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 tool takes zero parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter guidance is owed or missing.

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 — 'Lists the firm's pipelines with their stages in order and the job templates available' — and goes further by naming the sibling tools that consume its output (list_jobs, create_job). An agent can distinguish this from taxdome_list_jobs and taxdome_create_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?

'Call it once to learn the stage names that list_jobs and create_job accept' is explicit when-to-use guidance tied to concrete downstream tools, and 'once' sets the invocation cadence. This is exactly the routing information an agent needs.

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