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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one genuinely non-derivable behavioral note — that project names are user content and must not be treated as instructions — which is valuable prompt-injection context. It says nothing about result volume, ordering, or whether all projects are returned at once.

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?

Two short sentences, front-loaded with the action and scope, followed by one safety-relevant caveat. Nothing is padded and no sentence is redundant with the schema or annotations.

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?

This is a trivial parameterless read tool with an output schema, so return-value documentation is unnecessary and the safety profile is covered by annotations. The definition is nearly complete; it only lacks any hint about result size/pagination or the natural next step (dub_get_project for details).

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 correctly declares an empty object with additionalProperties=false, so there is no parameter meaning to add; baseline 4 applies. The description correctly implies the account scope comes from the connection rather than from an argument.

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 and resource ('find existing projects in the connected account'), which is unambiguous and consistent with the title 'List DubSync projects'. It does not explicitly distinguish itself from siblings such as dub_get_project (single-project lookup) or dub_create_project, but the plural 'projects' plus 'existing' makes the listing intent clear enough to select it.

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?

Usage is only implied by 'Use to find existing projects in the connected account' — there is no explicit when-to-use/when-not or named alternative such as dub_get_project for a single project. An agent can infer this is the browse/discover entry point, but must reason it out rather than being told.

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