font_analyze

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false) already convey the safety/idempotency profile. The description adds useful behavioral context the annotations lack: what is checked by default, what interpolation adds, and that the output is 'regional coverage and localized candidates, not artistic approval' with 'measurements and evidence_plan'. It does not explain why the operation is non-read-only/non-idempotent (likely report generation), leaving a 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?

It is compact and avoids padding, and the default checks are front-loaded. But the semicolon-packed, jargon-heavy prose is hard to parse and buries the top-level purpose, so the structure does not maximize clarity per token.

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?

An output schema exists, so return values need not be re-explained, and the description covers several behavioral/parameter facets. Still, with 5 parameters at 0% schema coverage, no usage routing among siblings, and no explanation of the non-read-only nature, it is only adequately complete.

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%, so the description must carry the load: it adds meaning for master_id ('Rules accept master_id or a variable location') and for interpolation ('adds timed source correspondence and compiled axis-grid checks'), and indirectly for detail ('Full reports include...'). It says nothing about revision or project_id, so compensation is only partial.

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 names concrete check categories ('visible ink', 'matching outlines', 'self crossings', 'digit spacing') and implies an analysis/QA role over a font project, so the general purpose is inferable. However it never states plainly what resource is being analyzed or how it differs from siblings like font_validate or font_release_check, and the dense jargon obscures the core purpose.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only conditional language ('by default', 'interpolation=true adds...') describes parameter behavior rather than the choice between this tool and its siblings.

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