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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the shape of what comes back (live/public timetable status, publishing horizon, tax and fee settings), which matters because there is no output schema; it does not say whether archived branches are included, ordering, or size of the result set.

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 front-loaded sentence that leads with the resource and then lists fields; every clause contributes information and nothing is repeated from the schema or annotations.

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-only list tool with no output schema, the description covers the return fields well enough for an agent to use the result. Minor gaps remain around scope (all branches vs. active only) and result ordering/pagination, but the core need is met.

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 the baseline is 4 and there is nothing for the description to compensate for. It correctly implies an unfiltered full listing by saying 'Every branch'.

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 concretely enumerates what a branch record contains (id, address, area, aliases, live timetable flag, publication month, tax/fee settings), so the resource and its payload are unambiguous, and combined with the name the read/list intent is clear. It does not differentiate against nearby siblings such as list_branch_lessons or get_overview, so it stops short of a 5.

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 save_branch, make_branch_live, list_branch_lessons, or get_overview, and no exclusions or prerequisites. The only usage signal is the tool name itself and the empty parameter list; the description text gives no guidance.

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