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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety baseline is covered. The description adds genuinely new behavioral context: the all-projects prerequisite connection, and an explicit prompt-injection warning about `{"untrusted_text": …}` fields being agent/repo-authored data rather than instructions.

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?

Front-loads what is returned and its scope before the prerequisites and the trust warning. Dense but every clause carries information; the untrusted-text sentence is arguably long but is a legitimate safety instruction, not filler.

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 still conveys the return shape (latest summary at a cadence level, containing agent/repo-authored text fields) and the access prerequisite. Only the return format details (size, which fields, formatting) remain unspecified, which is acceptable for a read tool.

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 only 50% — `level`'s enum is undocumented in the schema — but the description enumerates all five valid cadence values, closing that gap. It also adds the omission semantics for `project` (absent = all projects) that the schema's per-parameter description does not state.

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+resource ('latest written Chief summary') plus the cadence dimension and the two scoping modes (one project vs. all projects). This clearly separates it from siblings like get_project_status and get_updates, though it never names those alternatives explicitly.

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 one concrete usage condition — omit `project` to summarize across all projects, which requires an all-projects connection — but gives no guidance on when to prefer this over the other reporting siblings (get_project_status, get_updates, list_activity). Usage is implied rather than routed.

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