record_reverse_evidence

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

The annotation readOnlyHint=false already indicates a write operation. The description adds the specific behavior of 'append', which implies additive, non-overwriting writes. However, it does not disclose other important traits such as failure modes, requirements for existing artifacts, or side effects beyond appending.

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, efficient sentence with no wasted words. It is front-loaded with the primary action and object. However, given the tool's schema complexity, a slightly longer description with structured parameter guidance would be more appropriate.

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 tool with 10 parameters, a nested entry object, and no output schema, the description is far too incomplete. It does not explain return values, parameter semantics, or usage context. The agent would have to rely entirely on parameter names and the tool name to infer behavior, which is insufficient.

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 mentions no parameters. The schema includes 10 properties with 5 required and a nested entry object, but the description provides no hint about what the parameters mean, how they interrelate, or what values are expected. This is a severe deficiency for a tool with such a complex 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 action ('Append structured reverse-engineering evidence') and the target resource ('task artifact log'). It is specific enough to distinguish from many siblings, but it does not explicitly differentiate from similar logging tools like 'record_page_flow'.

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 no guidance on when to use this tool versus alternatives. It does not mention any preconditions, exclusions, or scenarios where another tool would be more appropriate. Given the large sibling list, this lack of usage context is a significant gap.

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