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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: it is a single round-trip aggregation, and it explains the provenance and purpose of the `workspace` field (users arriving from another app). It does not discuss freshness/staleness of the snapshot or auth prerequisites, so it falls short of a 5.

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 core purpose and well organized, but somewhat long. The 'collapsing whoami, describe_capabilities and describe_schema into a single call' clause is effectively repeated from the preceding sentence, and the closing workspace/why-it-exists sentence, while justified, could be tightened.

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 input schema and no output schema, the description carries the full burden of explaining return values, and it does so thoroughly — identity/org/plan, capabilities counts, schema index, task count, workspace URL, and web-only feature list. Nothing an agent needs to invoke it correctly is missing.

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 per the rubric the baseline is 4. The description mentions 'describe_schema(entity[, projectId])' but that documents a sibling's signature, not this tool's own inputs, so there is nothing further to clarify.

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 precise verb+resource ('cold-start summary for a fresh session, in one round-trip') and enumerates exactly what it returns (identity, org, plan features, capabilities summary, entity schema index, assigned-task count). It explicitly distinguishes itself from siblings by naming the three tools it collapses (whoami, describe_capabilities, describe_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?

Explicitly frames the use case ('fresh session', 'one round-trip') and routes the agent to alternatives for deeper needs: describe_capabilities for per-tool gates, describe_schema for field shapes, list_assigned_tasks for the full queue. Both when-to-use and when-to-use-something-else are covered.

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