jambavan_rin_mochan

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

With no annotations, description does well: discloses read-only nature, explains grouping by file, and flags markers without upgrade trigger as 'silently rot'. Enough for safe invocation.

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?

Three sentences: first states core action, second details findings grouping and flagging, third provides usage. No wasted words, front-loaded.

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 zero-parameter tool with no output schema, description adequately covers what it does (harvest markers, group, flag) and when to use. No missing critical context.

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?

Zero parameters, baseline 4. Description adds no param info but schema coverage is 100% trivially. No extra needed.

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?

Description uses specific verb 'harvest' and identifies 'rin markers' with clear definition. Distinguishes from sibling jambavan tools by specifying it extracts debt markers and flags silent rot.

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?

Explicitly states 'Read-only' and 'Call before a release or refactor sprint', providing clear usage context. Lacks explicit alternatives or when-not-to-use, but timing guidance is strong.

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