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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real value beyond them: a single round-trip replaces multiple calls, and 'no real send needed to find out' tells the agent it can probe send-capability without side effects. It stops short of discussing auth preconditions 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?

Dense and front-loaded — the snapshot contents and the routing question lead, and every clause carries information. It is a single long sentence that leans on parenthetical enumerations, which is efficient but slightly heavy for one line.

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 an output schema present, the description needn't re-explain return shapes, and it still names the key fields an agent will rely on. For a zero-parameter, read-only overview, nothing needed to call 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 the baseline is 4. There are no argument semantics to clarify, and the description correctly spends no words on 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?

States a specific resource (account overview) and enumerates exactly what it returns: org context, credential identity, send-capability flags, inventory counts, active blockers, and deploy identity. It explicitly positions itself as a 'strict superset of the legacy whoami + workspace_health pair', distinguishing it from the sibling usage_overview without opening either 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?

Gives an explicit trigger ('Use before any non-trivial workflow') plus the exact question it answers ('who am I, can I do X right now, and which deploy is serving me?'), and names the alternative it supersedes. Nothing about when-to-use is left to inference.

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