create_glyph

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

No annotations are provided, so the description carries full responsibility. It states the creation action but omits side effects such as behavior on duplicate glyph names, whether the new glyph becomes selected, reversibility, or prerequisites beyond an open font. For a mutation tool, this is a significant gap.

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 compact and well-structured with an 'Args:' list. Each parameter is on its own line with a concise explanation. The purpose is front-loaded, and there is no redundant fluff.

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?

The tool has no output schema, so the description should explain return values or error conditions. It does not mention what happens on success, what errors may occur (e.g., duplicate name), or if the glyph is selected after creation. While the essential creation action is covered, several operational details that an agent would benefit from are missing.

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 description compensates well. It explains each parameter with examples ('a.ss01', 'uni0041'), units ('font units'), and clarifies that 'paths' uses the same format as set_glyph_paths. This adds meaning far beyond the bare schema types and defaults.

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 the verb ('Create') and resource ('a new glyph') in the context of 'the open font', which distinguishes it from sibling operations like delete, rename, or duplicate. The purpose is unambiguous and specific.

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 implies usage for creating a glyph from scratch but does not explicitly contrast with alternatives like duplicate_glyph or set_glyph_paths. There is no 'when to use' or 'when not to use' guidance, only an implicit context of working with the open font.

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