get_project_brief

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that the brief is "evidence-backed" and itemizes its sections, which is useful context, but says nothing about pagination via `first`, auth requirements, or freshness/staleness of the aggregates.

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 dense sentence that front-loads the verb and resource before listing the brief contents; no filler or repetition. It is appropriately sized, though the content list is somewhat packed and would read better split from the transactional framing.

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 an aggregate read tool with four undocumented parameters, no output schema, and no usage routing, the description leaves out critical invocation details. An agent cannot determine valid owner/number formats, how `fix`/`first` affects results, or how this brief relates to the more granular sibling tools that produce the same sections.

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 description coverage is 0% across four parameters: owner, number, first (default 100, max 100), and includeArchived. The description never explains that owner/number identify the target project, that `first` caps how many items feed the brief, or what includeArchived does. With no schema text to fall back on, the description fails to compensate for the coverage gap.

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 gives a specific verb ("Return") and a concrete resource ("Project operating brief") and enumerates what the brief contains (status/priority counts, in-progress work, review queue, unassigned work, blockers), which lets an agent distinguish it from generic siblings like get_github_project_snapshot. However it never differentiates itself from close siblings such as get_github_project_brief_context, get_review_queue, get_unassigned_work, and get_blockers, whose outputs it overlaps.

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 when-to-use guidance, no when-not-to-use, and no mention of alternatives. An agent can only infer that this is an aggregate read because of the content enumeration; nothing tells it to prefer this over the individual review-queue/unassigned/blocker tools or vice versa.

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