Feedback Summary

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

Annotations already indicate readOnlyHint=true, and the description aligns with 'Get summary'. However, it fails to disclose any behavioral traits beyond what annotations specify, such as what constitutes 'recent' or the nature of the summary.

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 sentence with no fluff, but it is too sparse for a tool with no output schema and only one undocumented parameter. Conciseness is achieved at the expense of necessary detail.

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 no output schema and only one ambiguous parameter, the description provides insufficient information for an agent to correctly invoke the tool and interpret results. The term 'summary' is undefined, and 'recent' is not quantified.

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?

The single parameter 'recent' (type number) has no description in the schema or the tool description, leaving its meaning (e.g., days, hours, count) completely ambiguous. With 0% schema coverage, the description should clarify but does not.

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 it retrieves a summary of recent feedback, but the term 'feedback' is vague and does not differentiate from sibling tools like feedback_stats or capture_feedback.

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 on when to use this tool versus alternatives, such as feedback_stats for statistics or capture_feedback for entering feedback. The description lacks usage context.

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