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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral fact that the lookup is implicitly scoped by the MCP key rather than by user-supplied input. It still says nothing about what the response contains or what happens if the key maps to no project.

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?

A single short sentence with no filler, and the key concept (the MCP key→project binding) is stated up front. It is efficient, though so terse that it borders on under-specification for an agent that has never seen the tool.

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 simple, zero-parameter read tool with annotations covering its safety profile, so the description need not be long. However, with no output schema, the agent is left guessing what identity data is returned (project id, name, workspace), which is exactly the information a caller needs before depending on this 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?

With zero parameters, the baseline is 4, and the description earns it by explaining that the MCP key itself is the implicit input. This tells the agent why no arguments are needed, which the empty schema cannot convey on its own.

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 object: identifying the project tied to the MCP key. That is a clear read operation an agent can understand without opening the schema. It does not, however, differentiate itself from related siblings such as get_current_site, switch_project, or list_projects.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The agent must infer that this is a session/bootstrap call for discovering which project the credential belongs to.

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