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

Annotations already establish readOnly, idempotent, closed-world, and non-destructive behavior, but the description adds material context beyond them: the brief is null before the first one, the credential scope needed, the claimed-workspace requirement and 403 refusal, and the fact that approval is external to the analyst.

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-loaded with the core read action and return content, then prerequisites and edge case. The sentences are dense but every clause contributes useful selection or invocation information.

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?

Given zero params, no output schema, and clear annotations, the description is complete: it explains what the brief contains, the null-before-first behavior, the auth/workspace prerequisites, and that proposals are pending rather than applied.

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 schema imposes no semantic burden and the baseline is 4. The description does not need to explain parameter meanings and correctly focuses on the brief's content and prerequisites.

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?

Specific verb 'Read' plus resource 'latest weekly brief' written by the pricing analyst, and it enumerates exactly what the brief contains: claims, findings, and pending proposals with the exact applying call. It also distinguishes the brief from the act of applying proposals by stating the analyst never applies anything.

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?

Clear context for when to read it and strong prerequisites: a Last Price credential with routing read scope and a claimed workspace, with a sandbox key refused 403 until claimed. It does not explicitly name alternative tools or when not to use it, so it lacks a full when/when-not/alternatives matrix.

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