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

Annotations already mark it read-only and non-destructive, but the description adds substantial behavioral context: it is free and unauthenticated, deliberately requires no signature, and treats possession of the id as the entire authorization. Warning the agent to treat the id as a secret is meaningful beyond the schema.

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?

The opening sentence is useful and front-loaded, but the description drifts into an unrelated feedback pitch about POST /feedback and daily analysis. That content does not help an agent select or invoke the tool and makes the definition longer than necessary.

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 one-required-parameter read tool, the schema, annotations, and description together cover purpose, authorization model, and parameter semantics. The description does not explicitly describe the return shape, but the tool's name and flow make the returned briefing content fairly obvious.

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?

The schema already documents id as returned by handoff_deposit, so baseline is 3. The description adds value by explaining that the id is not just an identifier but the sole authorization credential and a secret, which affects how the agent should handle it.

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 states a specific verb and resource: 'read a briefing back by id.' It also anchors the tool in a clear flow by referencing handoff_deposit as the step that creates the briefing, making the tool's role and relation to siblings unambiguous.

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 gives clear usage context: this is how a purchased briefing 'reaches your successor over MCP,' implying it should be used after handoff_deposit. It does not explicitly name alternatives or state when not to use it, but the intended sequencing is evident.

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