hf

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

With no annotations, the description carries full burden but fails to disclose any behavioral traits such as side effects, permissions, or what happens during a handoff. Compact parameters like 'tk' (default 300) and 'q' are left unexplained, leaving the agent uninformed about the tool's behavior.

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 but not appropriately sized; it sacrifices necessary detail for brevity. Every sentence should earn its place, but here the minimal text leaves critical gaps. It is under-specified rather than concise.

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 complexity of 15 parameters, 0% schema coverage, and no annotations, the description is severely incomplete. It does not explain the tool's output (though output schema exists), nor does it provide enough context for the agent to use the tool correctly.

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%, and the description only lists 'act, st, prio, tk, q' as compact params without explaining their purpose, format, or constraints. For 15 parameters, the description adds no meaningful semantics beyond what the parameter names provide.

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 'Handoff: act=new (create) | act=get (read)' which suggests two modes but does not clarify what a handoff is or what resource it operates on. The term 'handoff' is ambiguous without further context, and the description provides no elaboration beyond the act values.

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 given on when to use this tool versus alternatives like 'task' or 'session'. There is no mention of prerequisites, use cases, or conditions that would help an agent decide between sibling tools.

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