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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, but the description adds zero behavioral context: no pagination behavior, no cursor semantics, no rate limits, no indication of what the history contains or how it is ordered. For a history-listing tool the description carries no additional information at all.

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 words is not conciseness but under-specification. There is no structure, no front-loading of scope, and nothing that earns its place because there is essentially no content.

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?

A five-parameter tool with a required id, a cursor, a limit, and a filter, with no output schema and no annotations beyond the safety profile, is left almost entirely undocumented. An agent cannot reliably invoke this correctly from the description alone.

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 roughly 80%, but the descriptions themselves are near-useless: 'id' is documented as 'id', 'include' as 'text', and 'agent' has no description at all. The tool description compensates for none of this, so the meaning of limit, before, agent, and include remains unclear.

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?

Tautological: description restates name/title.

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 guidance whatsoever on when to use this tool, when not to, or which sibling to prefer. An agent must guess between this and analysis_live_list, autopilots_logs, and list_deep_analyses with nothing to go on.

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