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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so richly. It explains when command fields are null, how commands depend on the detected environment, which runtimes are honored, that `comandos.agora` is a multiline block to run whole, and that unsupported formats are never guessed. This goes well beyond what a bare schema or annotation would convey.

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 dense but each sentence earns its place: purpose, view selection, environment constraints, script behavior, execution advice, and cron conditions are all covered without filler. The main purpose is front-loaded before the clarifying details.

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 and no annotations, the description is unusually thorough: it covers both views, null conditions, command generation, execution guidance, and format behavior. The main remaining gap is that it never explicitly defines the top-level response shape or precisely reconciles "measurements" with "collections," but that is a minor ambiguity for a list tool.

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 parametershare, so the schema coverage is complete by default. Per calibration, a zero-parameter tool starts at baseline 4 because there is no parameter meaning for the description to clarify.

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 opens with a specific verb and object, "Lists your measurements," and immediately states that entries carry commands adapted to saved device environments. It explains the two views, `coletas` and `equipamentos`, which gives useful detail about what the listing contains. It does not explicitly compare itself to sibling list tools, so it misses the highest level of differentiation.

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 in-tool guidance: use the `equipamentos` view unless a single measurement is genuinely desiredhola. It also sets behavioral expectations such as commands only being generated from detected environments and cron lines only being offered when crontab exists. However, it never names sibling tools or tells an agent when to choose `list_collections` over another listing endpoint.

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