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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description earns credit by disclosing the shape of the returned payload (switched-on state, jobs, triggers, deliverables, permitted acts), which matters because no output schema exists; it does not, however, mention result size, pagination, or whether inactive tommos are included.

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?

A single sentence with no filler, front-loaded on the resource being listed. The nested parentheticals ("what starts each, what it delivers") and the trailing em-dash clause make it dense to parse, but every phrase carries information.

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 read with no output schema, the description does the necessary work of outlining the return structure and the scope (this workspace, consistent with openWorldHint=false). It is slightly short of complete in that it never says how many tommos to expect or how to interpret a job's "acts" relative to read_an_act.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly conveys that the result is workspace-scoped and unfiltered.

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 resource (the tommos of this workspace) and enumerates exactly what each entry contains: on/off state, jobs with their triggers and deliverables, and each job's permitted acts. It is clearly a bulk read rather than a single-item read, which implicitly separates it from read_a_job and read_an_act, but it never names those siblings explicitly.

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 guidance on when to reach for this tool versus read_a_job, read_an_act, or the switch_* tools that also touch tommos. No prerequisites, no scoping advice, no indication of cost or size of the result set. The agent must infer the use case entirely from the resource name.

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