Get active work context

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

The description aligns with the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) by using 'Returns', and it adds genuinely useful behavioral detail by disclosing that the ticket mapping carries a confidence score — signaling the mapping may be imperfect. No error, rate-limit, or edge-case behavior is disclosed, but for a read-only no-parameter getter, the transparency is adequate and non-contradictory.

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?

Two tight sentences: the first front-loads the return payload with concrete fields, the second delivers the usage priority. Every word carries information; there is no filler, redundancy, or buried context.

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?

Given the tool's low complexity (no parameters, no output schema, simple annotations), the description covers the essential ground: what data comes back and when to call it. It does not describe the output format or edge-case behavior (e.g., what happens when no ticket is active), but for a simple getter the listed fields plus the 'call first' guidance are reasonably complete.

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?

With zero parameters and 100% schema coverage (empty object), there is nothing for the description to clarify. The rubric's baseline of 4 for a zero-parameter tool applies; the description correctly avoids inventing parameter explanations, so no deduction is warranted.

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 ('Returns') and names the precise resource and payload: the active ticket, repo path, today's commit count, and confidence in the ticket mapping. This clearly differentiates it from siblings like get_ticket_context (single ticket), get_today_commits (commit list), and get_eod_summary (end-of-day view), making the aggregate-snapshot purpose 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 explicit directive 'This is the primary context tool — call it first' gives strong, actionable guidance on when to invoke it as the entry point. It stops short of naming sibling tools or stating when NOT to use it (e.g., when a detailed ticket or commit breakdown is needed), but the priority instruction is clear and sufficient for an agent to sequence correctly.

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