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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that approval is a separate team decision, clarifying that this tool does not itself approve the request, but it provides no further behavioral detail (e.g., whose request is read, return shape). Given annotation coverage, this added context is modest but useful.

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 short sentences, front-loaded with the core action, and every sentence carries weight: the first states the operation, the second disambiguates approval scope. No filler or 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?

For a zero-parameter, read-only tool with rich annotations and no output schema, the description covers purpose and the key caveat that approval is out of scope. A minor gap remains: 'the person's' is ambiguous (likely the caller's own request given no parameters and a summer_account_me sibling), and the description does not clarify this.

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 are zero parameters, so the baseline for parameter semantics is 4. The description correctly adds no parameter details because none are needed, and the schema trivially documents the empty object.

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 states a specific verb ('Read') and resource ('person's Summer access request'), making the tool's purpose immediately clear. However, it does not explicitly name or differentiate itself from the sibling tool summer_account_access_request_submit, so it falls short of the highest bar for sibling differentiation.

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?

Usage is implied: read the access request. The second sentence ('Approval is a separate Summer team decision') gives a when-not hint by clarifying that this tool does not handle approval, but it does not name an alternative tool or state explicit conditions for choosing this over the submit sibling. This is implied usage rather than explicit guidance.

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