get_context

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

With no annotations, the description carries the full behavioral burden, and 'Read' does imply a non-mutating operation. It usefully signals that the response is an aggregate of several artifacts (spec, revision, evidence, handoffs), which is real behavioral context, but it says nothing about scoping, permissions, or whether the read is cached or live.

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 front-loaded sentence with no filler or repetition. It is efficient, though terse enough that it could have absorbed a routing clause without becoming bloated.

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?

Because an output schema exists, the return values need not be explained, and the description does list the artifact categories returned. What remains missing is the linkage to the required work_item_id and any signal of when this read is appropriate, so it is adequate but not complete for a context-gathering tool.

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%, so the sole required parameter 'work_item_id' is undocumented in both schema and description. The description alludes to a single item's context but never names or explains the identifier, leaving the agent to infer the parameter's meaning.

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 gives a specific verb ('Read') and enumerates the resources returned (spec, revision, evidence, role handoffs), so the agent knows this is a composite read of a work item's state. It is clearly distinct from the write siblings (create_work_item, update_work_item, record_evidence), though it never explicitly positions itself against list_work_items.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer that this is the read step preceding updates or handoffs, which is guesswork rather than instruction.

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