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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotence are covered by structured data. The description adds the fact that several distinct values are bundled into one response, but says nothing about format, whether any field can be null/absent, or what 'this connection's grant' means concretely.

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 front-loaded sentence with no filler. It is efficient, though it is essentially a verbatim copy of the tool title, which slightly reduces its marginal value.

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 is the only place return semantics can be conveyed, and it lists the four payload areas only at a high level. 'Summer access status' and 'this connection's grant' are left undefined, so an agent cannot predict the shape or possible values of the response 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. No parameter guidance is needed or missing.

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 enumerates the concrete resources returned (signed-in person, Summer access status, profile photo path, connection grant), which is far more informative than the cryptic tool name 'summer_account_me'. It stops short of distinguishing this from siblings that also surface identity/status data such as summer_client_status or summer_slack_identity_read.

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 statement of when to call this versus alternatives like summer_capability_checks_get or summer_account_connections_list. The agent must infer usage purely from the field list, with no exclusions or prerequisites offered.

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