List handoffs routed to a specialist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read nature is covered. The description adds the 'explicitly routed' qualifier but does not disclose additional behavior like pagination, default limit semantics, or response structure. This is acceptable but not rich 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 a single front-loaded sentence that directly states the tool's purpose without filler. Every word contributes, making it highly concise and well-structured.

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?

The tool is a simple read-only list with annotations and a minimal schema, so complexity is low. However, the description does not mention return format, pagination, or how 'routes' relate to handoffs in the workflow. It is minimally adequate but leaves room for contextual details that would help an agent fully use the 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?

With 0% schema description coverage, the description must compensate. It partially clarifies the 'target' parameter as a named specialist/agent, but it does not explain 'project' or 'limit' (e.g., what limit controls). The schema provides defaults and required flags but lacks semantic meaning, and the description adds insufficient value.

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 verb 'List' and the resource 'handoffs' with a specific qualifier 'explicitly routed to a named specialist/agent target.' This distinguishes it from sibling tools like read_handoff or route_handoff and aligns with the title.

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 guidance is provided on when to use this tool versus alternatives such as frontispice_list_updates or frontispice_read_handoff. The context of filtering by target is implied but not explicitly contrasted with other list/read tools, leaving the agent without clear decision criteria.

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