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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safe-read profile is covered. The description adds essentially nothing behavioral beyond that – no pagination, ordering, or volume disclosure, which matters for a history-listing tool. With annotations carrying the safety burden, this is a modest 3.

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?

A single lean sentence with no filler and the subject front-loaded. It is not padded, though it is so terse it sacrifices useful context for brevity.

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 needn't be explained, but for a history-retrieval tool the description omits ordering, time scope, pagination, and what a 'message' even is. Against a very crowded sibling namespace, this is too thin to guide correct invocation.

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 coverage is 100% and the single project_id param is fully documented in the schema, so baseline 3 applies. The description adds no format or constraint detail beyond what the schema already provides.

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 states a specific verb ('Get') and resource ('message history') scoped to a project, which is clearer than the sibling 'projects_get'. However, among dozens of project-scoped siblings it doesn't differentiate itself beyond name, and 'message history' scope (what messages, from where) is left unstated.

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?

No when-to-use guidance, no prerequisites, and no reference to alternatives. Given the crowded sibling set (projects_get, projects_overview, projects_list), an agent gets no routing help about when message history is the right call versus other project reads.

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