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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing that this returns a composite (narrative brief plus a filtered card set), but it says nothing about freshness, scope, or volume of the returned cards. Modest added context beyond annotations.

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, front-loaded with the resource, with a tight parenthetical that defines the vague term 'brief' and a final clause naming the secondary payload. No waste.

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 a zero-param, read-only tool with no output schema, the description carries the return-value burden and does so at a high level — narrative brief plus pending cards. It is adequate, though it omits any hint about how large or how stale that content may be.

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, and schema coverage is 100%, so there is nothing for the description to compensate for. Baseline of 4 applies for a no-parameter tool.

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 resource ('the agent's most recent brief') and elaborates the contents (what happened, what it did, what needs the user) plus a secondary payload ('cards still waiting for a decision'). This is clear, though it does not explicitly distinguish itself from nearby siblings like list_cards or who_is_waiting_on_me that overlap with the 'cards waiting' and 'needs the user' content.

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 never says when to choose this over alternatives. With siblings such as list_cards, get_activity, and who_is_waiting_on_me covering adjacent ground, the agent is left to infer that this is a combined snapshot. No conditions or exclusions are given.

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