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

The annotations already establish that this is a safe read-only, non-destructive operation. The description adds useful behavioral context by stating that results include role and websites and that the tool supplies projectIds, though it does not discuss pagination or rate limits.

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 description is two short sentences with no wasted text. The core purpose and the workflow hint are both front-loaded.

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 parameterless read-only lister with annotations covering safety, so the description supplies enough context for correct invocation. It partially describes the returned project data but does not fully explain pagination or all response fields, though no output schema is available to rely on either.

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 no parameters, so there is no parameter-level ambiguity. Schema coverage is 100% and the description does not need to compensate for undocumented inputs.

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 gives a specific verb and resource: list the signed-in user's Projects, including role and websites. It implies a distinction from lower-level tools by saying it is the starting point for obtaining a projectId, but it does not explicitly differentiate from nearby list tools such as list_sites.

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?

The phrase 'Start here to get a projectId' gives clear workflow guidance for when to use this tool before other project-scoped calls. It does not provide when-not guidance or name alternatives, so it falls short of a full usage-guidelines statement.

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