capture_feedback

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

Description claims 'Capture' (write operation) contradicts annotations readOnlyHint=true, a serious inconsistency. Does not disclose what side effects occur (e.g., storage, persistence).

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?

Two sentences with no fluff. First sentence states core purpose, second adds key behavioral nuance. Efficient and well-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?

With 13 parameters, no output schema, and many sibling tools, description is too sparse. Does not explain when to use optional fields, what the return value is, or how different feedback paths work.

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?

Low schema description coverage (38%). Description adds no parameter details; only mentions 'up/down signal' and 'one line of why', which loosely maps to 'signal' and 'context' but not explicitly.

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 clearly states it captures an up/down signal and a reason, and distinguishes from memory promotion by mentioning vague feedback handling. Action and resource are specific.

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?

Description implies when to use (precise feedback) and what happens with vague feedback (logged and clarified, not promoted). Lacks explicit alternatives but provides context.

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