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

Annotations already declare readOnlyHint=true and the description confirms it with 'Read-only'. Beyond that it discloses genuinely useful behavior: token pinning rules, that all session reads/writes land in this project, and that other projects' resources are invisible from here. This is real context the annotation does not carry.

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 action and the token-pinning caveat are front-loaded, then the usage trigger, then the safety note. It is dense and a bit clause-heavy in the middle sentence, but every sentence earns its place with no 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?

For a zero-param, read-only lookup with no output schema, the description covers what the tool resolves and the scoping implications that matter for correct downstream calls. It does not describe the returned object's fields, but that is a minor omission given the tool's simplicity.

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?

Zero parameters, so there is nothing to overload or misdescribe - the schema is an empty object and the baseline for a no-param tool is 4. The description correctly implies no inputs are needed.

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 (returns the current project) and nails the scope semantics: an MCP token is pinned to its minted project, while a session token follows the member's current project. This distinguishes it clearly from project-oriented siblings like list_projects or move_cluster_to_project.

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?

Gives explicit trigger conditions - use first when a request says 'this project' or when a listing looks incomplete - which is exactly the routing guidance an agent needs. It lacks an explicit named MCP alternative/when-not, instead referencing the CLI twin `ankra project current`, so it stops just short of a 5.

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