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

No annotations are provided, so the description carries the full burden. It usefully discloses that the operation does not mutate status, its main behavioral trait, but says nothing about permissions, pagination, or the default limit behavior. Adequate but thin for a zero-annotation tool.

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?

Three short sentences, zero waste, with the core action front-loaded and the read-only clarification last where it lands hardest. Nothing is repeated from the schema or padding.

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?

An output schema exists, so return values need not be described, and the three optional filters are at least named. Still missing are the default limit of 50, whether results are paginated, and how department values map to real departments, leaving some gaps for an unannotated 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?

Schema description coverage is 0%, so the description does the work of explaining two of three parameters. It adds real value by naming the allowed status values (proposed or accepted), which the schema lacks as enums, but gives no guidance on the department filter's format or the limit semantics.

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?

States a specific verb and resource ("Read org lessons from SharedBrain") and hints at its read-only nature relative to the sibling accept_lesson via "Does not change status." It stops short of explicitly naming the write sibling, so the differentiation is only partial.

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?

Implied usage: the tool lists lessons and can filter by status/department, and the final sentence signals it is not the path for status changes. However, it never names accept_lesson as the alternative for accepting a lesson or states when an agent should prefer this over other intel tools.

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