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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the shape of the payload: standing preferences, past decisions, the team's pending Dora suggestions, and kept suggestions she flagged as clashing, repeated, or out of date. With no output schema, this content disclosure is the main behavioral signal, though it omits ordering, limits, and pagination.

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 opening clause front-loads the resource well and the middle sentence is short and directive. The closing sentence ('kept ones she flagged as clashing, repeated, or out of date') is grammatically tangled and its referent is unclear, costing more parsing effort than the information warrants.

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 two-parameter read-only list tool with no output schema this is passable, but key operational facts are missing: what the default scope is when neither optional ID is supplied, whether the two IDs are mutually exclusive, and roughly what the response contains structurally. The description covers content semantics but not invocation semantics.

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 100%, and the description's parenthetical '(orgId)' for company rules merely echoes the schema. It refers to 'a client's rules' without ever naming workspaceId, so it adds no syntax, exclusivity rule, or precedence behavior beyond what the schema already states.

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 names the resources involved (client rules, decisions, company rules, Dora's pending suggestions) but never states an explicit verb such as 'list' or 'returns'; the reading is inferred from the tool name. It also does not distinguish itself from siblings like search_library, get_library_item, or search_company_library, which an agent must resolve on its own.

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?

'Follow them in any work for the client' tells the agent what to do with the content, not when to call this tool. There is no guidance on when to use list_library_rules versus search_library or get_library_item, and no note on what happens when both orgId and workspaceId are omitted.

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