get_handoff_snapshot

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint, so safety is covered. The description adds that it's a single API call, groups results by state, and highlights idle tickets, which is useful behavioral context. But it doesn't specify what happens when no projects are given beyond 'all accessible', or how states map to results.

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 compact and front-loads the core purpose, then uses a labeled Args block that is easy to scan. A slight deduction because the states default list is long and could be trimmed, but every sentence earns its place.

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 snapshot with an output schema and clear sibling contrast, this is mostly complete. It could state that handoff values are YouTrack-specific or note the absence of pagination, but the core invocation knowledge is present.

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%, so the description must carry the meaning, and it does: projects, states, stale_days, active_within_days, and instance are all explained with defaults, formats (comma-separated), and special values. This fully compensates for the empty schema descriptions.

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 clearly states the tool takes a snapshot of tickets in handoff states, groups by state/dept, and contrasts it with track_cross_dept_journey. This gives a specific verb, resource, and scope that differentiates it from siblings like get_stuck_handoffs, search_issues, and track_cross_dept_journey.

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?

It explicitly positions usage as a fast single-query view complementing the richer per-issue track_cross_dept_journey, and the argument docs give concrete guidance (e.g., active_within_days=14 for 'currently in flight'). This is strong when-to-use guidance.

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