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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add operational context — and it does: default ordering is newest-first and visibility is role-dependent for experts. That assignment-scoping rule is genuinely useful behavior not derivable from the annotations or schema. It stops short of pagination/limit behavior, so not a 5.

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?

Three short sentences with the core action and ordering front-loaded, followed by filter and visibility notes. Nothing is padded; the only cost is that the role caveat is attached as a trailing clause rather than a clearly separated note.

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?

An output schema exists, so return shape needn't be described. For a two-parameter, zero-required read tool with annotations carrying the safety profile, the description covers purpose, ordering, filtering, and visibility adequately; only limit behavior is unaddressed.

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% for two parameters. The description addresses status by loosely glossing the states it filters over (drafts awaiting approval, approved pieces in progress, finished), which adds semantic meaning to the enum. The limit parameter is never mentioned, so half the parameters remain unelaborated — enough for a 3, not full compensation.

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 and resource ("List the workspace's content briefs") and adds useful scope: ordering (newest first) and the breadth of states covered (drafts, approved, finished). An agent can distinguish it from the singular get_brief by the plural list semantics, but no sibling tool is named explicitly, which keeps it at 4 rather than 5.

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 description implies usage (browse the brief backlog, optionally narrow with a status filter) and adds a role-scoping caveat ("An expert sees only the briefs assigned to them"). It never states when to prefer this over siblings like get_brief or list_articles, and gives no conditions or exclusions, so this is implied guidance rather than explicit routing.

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