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

With no annotations, the description carries the behavioral burden. It adds context by mentioning 'current live queue items' and 'personalised suggestions,' indicating fresh, identity-aware data. However, it does not explicitly state that the operation is read-only, mention permissions, or describe failure behavior.

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 only two sentences and contains no filler. It is concise, though the first sentence is an elliptical noun phrase rather than a complete statement of functionality.

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 simple one-parameter tool, the description conveys the tool's purpose and the nature of its output, but it lacks detail on how to select the task and what the returned runbook structurally contains. With no output schema or annotations, a bit more detail would make it fully self-sufficient.

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 a single 'task' parameter with an enum but no descriptions, giving 0% schema description coverage. The description does not explain how to choose a task value or what each enum option represents, leaving the agent to infer meaning from the enum names alone.

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 identifies the resource (runbook) and its contents: one stable task method and current live queue items. It is reasonably clear that this tool provides a runbook, though it stops short of an explicit 'retrieves/returns' verb and relies partly on the tool name.

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 second sentence explicitly tells the agent when to use the runbook: for method and for personalized suggestions in identity-aware target selection. It does not explicitly state exclusions or alternative tools, but the guidance is direct and usable.

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