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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that it lists requests. It does not mention whether the operation is read-only, how the optional status filter affects results, whether there is pagination, or any other behavioral traits an agent needs to know.

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 a single sentence with the verb leading, making it concise and front-loaded. However, it is under-specified, which is penalized elsewhere, but for the content it does include, there is no waste.

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?

Given the simple one-parameter tool, the description is still insufficient for an agent to understand the purpose and invocation correctly. It omits any explanation of the status parameter, the meaning of 'publication requests', and the intended user/context, making it incomplete despite having an output schema.

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 schema has one parameter 'status' with no description, and the tool description does not mention it at all. With 0% schema description coverage, the description needed to compensate, but it fails to provide any meaning or usage details for the parameter.

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 uses a specific verb 'List' and a clear resource 'librarian publication requests', which distinguishes it from sibling list tools like list_notes and list_reviews. However, it leaves some ambiguity about what exactly constitutes a 'publication request' or who the intended audience is, so it's not a perfect 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?

The description provides no guidance on when to use this tool versus alternatives, such as list_notes or list_reviews. There is no mention of prerequisites, typical use cases, or exclusions, leaving the agent without context on when this tool should be selected.

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