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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is fully covered. The description adds genuine value by enumerating returned content (outgoing applications with handshake and booking state, plus inbound anonymous pitches), but says nothing about volume, ordering, or pagination for what could be a large aggregate, and there is no output schema to fill that gap.

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 sentence with zero filler. The subject ('the signed-in person's pitches and bookings') is front-loaded and the two data categories follow immediately as elaboration, so the reader gets scope before detail.

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 parameters and no output schema, the description carries most of the burden of explaining what comes back, and it does so reasonably well by naming both directions of data and the associated state fields (handshake, booking state). The remaining gap is aggregate behavior — result size, ordering, or whether anonymous pitches are summarized — which an agent would need for a tool that can return two different record types at once.

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, which is the baseline 4 case. The description correctly implies no input is needed because everything is derived from the authenticated identity, matching the empty schema.

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 implied by 'read' plus a clear resource: the signed-in person's pitches and bookings, split into applications sent by their teams and anonymous pitches received on their own briefs. It distinguishes itself from singular readers like read_booking or read_brief by scoping to the caller's own two-sided activity, though the phrase 'on both sides' is slightly awkward and requires the following clause to disambiguate.

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?

The 'signed-in person's' framing implies this is a no-argument self-lookup, so an agent can infer it needs no identifiers or filters. However, no alternative is named: it never says whether to use this instead of read_booking for a specific bookingId, or instead of read_pitchable_briefs when browsing. Usage is implied rather than directed.

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