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

With no annotations, the description carries the full behavioral burden and does meaningful work: it declares the workspace is private (per-caller scoping), warns that evidence is untrusted content (prompt-injection hazard), and states an API key is required. It omits return shape and pagination/volume behavior, which keeps it short of 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, each earning its place: scope/mode first, then the safety caveat, then the auth requirement. No filler and nothing buried.

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-optional-parameter read tool with no annotations and no output schema, the description covers scope, auth, and the untrusted-content caveat. Only listing volume/pagination and a hint at what an issue record contains are missing, which is minor here.

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 0% for the single optional issue_id, so the description must compensate. It conveys the pivotal semantic — pass an ID to get one issue, omit it for the workspace — but says nothing about the UUID format or validation that the schema carries only structurally.

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 — read the private delivery-issue workspace — and distinguishes the two modes (whole workspace vs. one issue by ID). It doesn't name the sibling update_delivery_issue as the write counterpart, but the read verb is unambiguous next to it.

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?

"or one issue by ID" implicitly tells the agent to supply issue_id for a single fetch and omit it for the workspace, which is the key usage decision. There is no explicit when-to-use versus update_delivery_issue or other delivery tools, so the guidance remains implied rather than stated.

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