get_handwriting

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

With no annotations, the description carries the behavioral burden. It states this is a read operation, returns a PNG, and has a precondition (user has already written something). It does not describe failure behavior if called prematurely, but the explicit 'only call after' warning makes the main risk visible.

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 front-loaded with the core purpose, then gives return type, precondition, triggers, and an exclusion in compact form. Every sentence adds useful selection or invocation guidance without unnecessary filler.

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 zero-parameter tool with no output schema, the description adequately covers what the tool does, what it returns, and when it should be called. It could be slightly more complete by contrasting with recognize_handwriting, but the essential invocation context is present.

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 and the schema has no properties, so there is nothing for the description to clarify. The baseline for zero-parameter tools is 4, and the description appropriately says nothing misleading about inputs.

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 action ('Read the user's CURRENT handwriting from the tablet') and the return type (PNG image). It is specific about the resource and timing, but it does not explicitly distinguish this from the sibling recognize_handwriting, so full differentiation is left to inference.

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 gives explicit when-to-use conditions ('Only call this AFTER the user has written something and asks you to look'), concrete trigger phrases, and a clear when-not-to-use instruction with the alternative named ('Do NOT call this for initial setup — use get_connection_info first'). This is strong guidance.

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