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

With readOnly/idempotent/non-destructive already in annotations, the description adds substantial context beyond them: the 12-image cap, which links get dropped and named for get_frame, what each frame contains (drawing rendered in, pointing links, shared screen), the exclusion of webcam frames, and that returned links are unauthenticated and expire after 'some hours'. These are operational traits annotations cannot express.

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 critical routing instruction is front-loaded, but the body is two sprawling run-on sentences packed with parenthetical asides that are hard to parse. The content is mostly relevant, yet density and length work against quick comprehension.

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?

There is no output schema, so the description carries the burden of explaining returns — and it does: frame contents, labelling, the [FRAME N] transcript marking, image cap, and the two link forms (Link vs Media only) with their fetchability and expiry. An agent can act correctly without further information.

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?

Only one parameter, and the schema description (100% coverage) already states it is the id field from feedback_list, feedback_get, recent_activity, search or wait_for_feedback. The description repeats that sourcing information rather than adding new meaning, so baseline 3 applies.

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 opens with a concrete verb+resource: 'The visuals of a feedback item, in one call', and immediately specifies which items qualify ('any item with a visuals field'). It also distinguishes itself from the closest sibling by stating 'Use get_frame only for a moment this did not show.'

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?

Explicit when-to-use ('call it before acting on any item with a visuals field'), when-not/alternative ('Use get_frame only for a moment this did not show'), and what is out of scope ('webcam frames are NOT included'). The agent has no inference left to make about tool selection.

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