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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses where credentials come from (hosted API key vs. local AALY_TOKEN JWT/API key), what is fetched (platform user record), the exact return surface (user, projects with id/slug/name, key context, default_project_id, hint), and a behavior-changing side effect on other tools. No contradiction with the read-only annotations.

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 the critical instruction ('ALWAYS CALL THIS FIRST') and every subsequent clause carries functional information about credentials, return shape, and downstream effects. It is dense to the point of being a long single block, but no sentence is filler.

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?

There is no output schema, so the description carries the return contract itself, and it does so by enumerating the returned fields including the `hint`. Together with the credential-source detail and the default_project_id effect, an agent has everything needed to call this correctly on the first turn.

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 and the description correctly states 'No parameters.' The discussion of project_id applies to other tools rather than this one's inputs, but it usefully frames why no parameter is needed here.

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?

Names a specific verb and resource set: it resolves identity from the request token, fetches the user record, and lists projects under the customer. This is clearly differentiated from the sibling list_projects (which lists projects without resolving identity) and from every create_/update_/delete_ sibling.

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?

Explicitly states 'ALWAYS CALL THIS FIRST in any new conversation', which is about as strong a when-to-use directive as exists. It further explains that a returned default_project_id lets callers omit project_id on create_entity/generate_openapi_spec/describe_project/update_project, so the agent knows the downstream consequences of calling this first.

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