micropython_get_info

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

No annotations exist, so the description carries the full burden. It usefully enumerates the fields that may appear in info (platform, version, free_mem, fs_free_kb, etc.), which is real added context. However, it omits whether a connection is required, whether it blocks, and any permission/cost considerations for a hardware round-trip.

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 one-line Japanese purpose is well front-loaded, but the Returns block restates fields that an output schema already exposes, and the Notes list is somewhat sprawling across many short lines. Some of that structure duplicates structured data rather than earning its place.

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?

With an output schema present, explaining return values is not strictly necessary, yet the Notes on info contents do add value beyond it. The description is nonetheless incomplete on operational context: no mention of a required connect step, connection failure behavior, or relationship to micropython_connection_status.

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 takes zero parameters and the schema is fully described, so per the baseline convention a 4 is appropriate. There is nothing parameter-related for the description to add or omit.

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 states a specific verb+resource: retrieving device information from the MicroPython board. That resource is not shared by any sibling tool, so an agent can distinguish it. It does not, however, explicitly differentiate itself from the nearest adjacent tool (micropython_connection_status).

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 statement of when to call this versus alternatives, no prerequisite (e.g. an active connection via micropython_connect), and no exclusions. Usage is only implied by the tool's nature as a read-only getter.

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