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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, so the safety profile is covered. The description adds valuable context beyond them: the connection prerequisite, the specific fields returned per environment, and the recommended downstream handoff.

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?

Front-loaded with what is listed, followed by the prerequisite and the follow-up routing to import_dbt_lineage. Three sentences, each carrying information, though the connection-setup detail could be trimmed slightly.

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?

With no output schema, the description compensates by summarizing the returned environment fields and mentioning jobs. Combined with the prerequisite and downstream usage, it is nearly complete for a no-arg list tool.

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, so the baseline is 4; there is no parameter surface that the description needs to explain.

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+resource: listing the connected dbt account's environments (with id, name, type, project) and jobs. The name/title emphasize 'jobs' while the description foregrounds environments and jobs equally, but an agent can still tell this apart from siblings like list_snowflake_databases. It names import_dbt_lineage as the downstream consumer, aiding differentiation.

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?

Gives a real prerequisite (the user must connect dbt under Settings > Connected apps > dbt Cloud) and states what to do with the output (pass a deployment environment_id or job_id to import_dbt_lineage). It doesn't explicitly say when NOT to call this tool, so it falls just short of 5.

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