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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds non-annotation context: an auth/account requirement and the fact that quota-style 'Suite runs left' is returned alongside project metadata. It stops short of noting result size or ordering, but for a zero-argument personal list that is minor.

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 short sentences with no filler: resource and return shape first, usage/routing second, prerequisite last. Every clause earns its place and the routing guidance is front-loaded where an agent will read it.

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 parameters, no output schema, and full annotation coverage, the description covers what the agent needs: what it returns, when to call it, and the account requirement. The phrase 'Suite runs left' is slightly cryptic and its units/meaning are never explained, which is the only real gap.

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, which sets the baseline at 4. The description instead characterizes the response contents (id, name, pack type, status, Suite runs left), which is useful orientation even though it does not substitute for parameter documentation that does not exist.

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 ('The user's Design Studio packaging projects') and enumerates the returned shape (id, name, pack type, status, Suite runs left). It also names the sibling tools it precedes (compare_packaging_options, post_rfq), so an agent can distinguish it from the rest of the list 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?

Explicit triggering condition: use it 'when the user refers to "my project" without an id,' and it names the downstream tools that depend on its output. It also states the account prerequisite ('Requires the user's OPN account'), leaving nothing to inference.

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