list_legacy_font_assets

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

Description implies a read-only operation but does not explicitly state safety, permissions, or performance traits. With no annotations, the description could add more behavioral context, though the tool is simple and likely safe.

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?

Single sentence, highly concise, with no redundant information. Every word adds value.

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 the simplicity (no parameters, no output schema), the description fully covers what the tool does and what it excludes. No gaps remain.

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 tool has zero parameters, so the description adds no additional meaning beyond the schema. Baseline score of 4 applies as per rules for 0 parameters.

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?

Clearly states it lists legacy font assets, specifies file extensions (.fontsettings, .ttf, .otf), and explicitly excludes TMP, which distinguishes it from sibling list tools.

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 makes it clear what assets are covered and what is excluded ('not TMP'), providing implicit guidance on when to use it versus other list tools, though explicit when-to-use or when-not-to-use statements are missing.

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