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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description does add value beyond them: it discloses the full breadth of the payload and implies a freshness/staleness concern via 'read again before changing a list'. However, it gives no warning that this is a large, whole-account payload — the single most important behavioral fact about an everything-read tool — and says nothing about cost or caching.

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?

Two sentences, no waste. The content enumeration is front-loaded so an agent knows the payload scope immediately, and the operational instruction follows rather than burying it. The long list is load-bearing — each item is a distinct section the agent would otherwise have to discover.

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 output schema, the description carries the burden of describing return contents, and it does so by enumerating the sections an agent will receive. The remaining gap is shape and scale: it doesn't indicate how large or deeply nested the returned object is, so an agent can't anticipate payload size before calling.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering or scoping options exist, matching the empty schema with additionalProperties: false.

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 ('The whole Portal in one read') and then enumerates exactly what that covers: business, plan/billing state, team, assistant settings and tone, documents and reading state, activation flags, Needs you topics, sign-off. That enumeration separates it in practice from narrower siblings like get_setup_status, get_my_standing and get_team_board. It stops short of naming those alternatives explicitly, so sibling differentiation is implied rather than stated.

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?

'Start here' is an explicit entry-point instruction, and 'read again before changing a list' gives a concrete pre-mutation re-read rule, which is real usage guidance rather than filler. What's missing is the negative case: nothing says when to prefer a narrower sibling (get_setup_status, get_my_standing) instead of pulling the entire Portal.

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