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

Annotations already cover safety with readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds useful behavioral context beyond that. It discloses partial-failure behavior, including unavailable visibility when there is no completed run or when metrics are still pending and should be retried later.

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?

The description is front-loaded with the core purpose and then explains scope and failure behavior. It is dense but not padded; the long enumeration of sections earns its place by summarizing what each section returns.

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 multi-section overview tool with no output schema, the description is complete enough to call correctly. It explains the aggregate nature, the available sections, section selection, and expected partial unavailability such as no_completed_run and metrics_pending.

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?

Schema coverage is 100%, so the schema already documents project_id and the sections enum. The description still adds useful meaning by clarifying that omitting sections returns all, passing fewer sections reduces response size, and profile includes owned domains and competitors.

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 uses a specific verb and resource: read one project overview in a single call. It distinguishes this aggregate tool from the many sibling read_* tools by stating that each section is a short summary and the matching read_* tool provides depth or paging.

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?

It gives explicit usage guidance: use this first to orient, then use the matching read_* tool for depth or paging. It also explains how to control scope by omitting sections for all or passing a few to keep the response small.

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