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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the response includes the current revision and the change history, which is real behavioral context beyond the annotations. It does not say what is returned when no reader connection is configured or whether elevated permissions are required.

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 the verb first; given there is no output schema, the enumeration of what is returned (reader mode, connected state, revision, history) is largely justified rather than filler. The duplication of the title verbatim is the only real redundancy.

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 does a decent job of naming the returned fields, and the sole parameter is fully documented in the schema. However, it omits edge behavior (no connection present, permission requirements) and any indication of response shape beyond a field list.

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?

There is a single parameter with 100% schema description coverage ('Summer company ID' with a UUID pattern), so the schema carries the semantics. The description adds nothing about the company parameter, its format, or scoping behavior — baseline 3 applies.

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 names a specific resource — the identity/connection Summer uses to read Slack — and enumerates the distinguishable modes (Summer app, installer's personal read access, AI employee, admin's Slack account) plus the returned revision/history. That is well beyond a bare name. It never references a sibling such as summer_slack_reader_update or summer_slack_identity_read, so the agent gets no explicit routing signal, and the text is a verbatim copy of the title.

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 (e.g., use summer_slack_reader_update to change the reader, summer_slack_identity_read to check Slack identity), no prerequisites such as admin permissions, and no exclusions. Usage must be inferred purely from the 'read' in the name.

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