adobe_fonts

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

The annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is fully covered. The description adds that output includes exact PostScript names, which is useful, but it never states the required application parameter or any scoping/limit behavior.

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?

One front-loaded sentence with no filler, and the most important output detail (PostScript names) lands immediately. It is arguably too short rather than too long.

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 tool whose only parameter is required and completely undocumented, and whose listing is presumably per-application, the description omits the one fact an agent must know before calling it. The output schema covers return values, so that omission is acceptable, but the input scoping gap is not.

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 description coverage is 0% and the single required parameter ("application", enum photoshop|illustrator) has no documented meaning anywhere. The description never mentions that an application must be supplied or what selecting one changes about the returned font set, so it fails to compensate for the schema gap.

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 gives a specific verb+resource ("List native font families, styles and exact PostScript names") and is unmistakably distinct from every sibling, none of which touch fonts. It stops short of saying the listing is scoped to a single application, which is the one qualifier an agent needs.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only implicit signal is that the result is useful when the agent needs font identifiers, which an agent must infer on its own.

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