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

With no annotations provided, the description carries the full burden. It discloses conceptual context (media blocks are pipeline building blocks) and the valid category surface, but says nothing about the return shape, result volume, or whether this is a pure read operation — leaving meaningful gaps for an unannotated tool.

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: purpose first, then the category enumeration that makes the parameter usable. The long list is dense but every term is a valid filter value, so nothing is wasted.

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 single-optional-parameter list tool with no output schema, the description covers purpose, filtering behavior, and the category vocabulary. Only the shape of the returned listing is left unstated, which is a minor gap at this complexity.

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 coverage is already 100%, so the baseline is 3; however, the description enumerates roughly twenty valid category names far beyond the three examples in the schema, materially improving the agent's ability to pick a correct filter value.

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?

States a specific verb and resource ('List available VisioForge media blocks') plus the filtering scope. It does not explicitly distinguish itself from the sibling get_media_block_info, so an agent must infer that this lists while that one fetches details of a single block.

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?

Usage is implied through 'optionally filtered by category' and the note to leave the filter empty to list everything. There is no explicit guidance on when to prefer this over get_media_block_info or when a filtered vs unfiltered call is appropriate.

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