get_active_work

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read' matches that. The description adds a vague scope qualifier ('visible', 'active') but does not clarify what 'visible' or 'active' mean operationally, nor does it disclose filtering, permissions, or output behavior beyond the 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?

The description is very short and front-loaded, with no filler words. However, the brevity crosses into under-specification because key concepts like 'active work' and 'visible' are not explained, making the definition terse rather than sufficiently informative.

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 read-only tool with one optional parameter and no output schema, some ambiguity might be tolerable, but the description does not explain what 'active work' is, what the response contains, or how this relates to threadId. An agent lacks enough context to confidently invoke the tool or interpret its result.

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 has one parameter, threadId, with no description and 0% schema description coverage. The description does not mention threadId or explain its effect, so the parameter's meaning is left to its name and type alone. The description fails to compensate for the absent schema documentation.

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 uses a specific verb ('Read') and names a resource ('visible active work'), so it is not a tautology. However, 'active work' is ambiguous and the description does not differentiate this tool from sibling read tools such as get_thread or list_threads. An agent would still have to infer what 'active work' means.

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?

No when-to-use guidance or alternatives are provided. The description does not explain when to choose get_active_work over sibling tools like get_thread, get_thread_messages, or list_projects. This leaves the agent to guess the tool's specific role.

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