rubeus_harvest

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

No annotations are provided, so the description carries the full burden. It mentions looping and optional auto-renewal, but does not disclose side effects (e.g., whether tickets are removed from the source), authorization needs, or destructive potential, which is insufficient for a monitoring/ticket extraction tool.

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 extremely concise, with three short sentences. Every sentence adds value—first states the action, second elaborates on loop and auto-renewal, third gives use case. No fluff.

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 has 6 parameters and no output schema. The description lacks details on return values or output format, which is critical for an agent to process results. It also does not explain how 'runfor' interacts with the loop or what 'harvested' means in terms of output, leaving significant gaps.

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 100%, so baseline is 3. The description does not add meaning beyond the schema; it does not explain how parameters like 'monitorinterval' or 'registry' affect behavior, relying entirely on the already documented schema.

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 monitors and harvests TGTs continuously, with specific verb 'harvest' and resource 'TGTs'. It distinguishes from siblings like rubeus_asktgt or rubeus_dump by focusing on capturing new tickets from other users.

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 description provides a usage scenario: 'Useful for capturing tickets from other users logging in.' However, it lacks explicit when-not-to-use guidance or comparison with alternatives, leaving the agent to infer context.

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