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

Annotations already cover readOnly, idempotent, non-destructive, closed-world, so the safety profile is free. The description adds genuinely new context: the authentication requirement (OAuth or API key) and the newest-first result ordering, both of which affect how an agent plans the call.

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?

Two sentences, front-loaded with the resource and payload, followed by the use case and examples. The examples and the auth sentence both earn their place, though the parenthetical field list is slightly dense.

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?

With no output schema, the description usefully enumerates what comes back, and it covers auth. However, for a paginated list tool with limit/offset parameters it says nothing about paging behavior or result-set size limits, which is the main operational gap.

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 0%, so limit and offset are entirely undocumented in both schema and description. The description never mentions pagination, page size, or defaults, leaving the agent to guess how these two integer parameters behave.

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?

States a specific verb and resource ('Lists the analysis projects the user already has') and adds the returned fields (id, name, response count, credit status) plus ordering (newest first). This clearly separates it from single-project siblings like open_end_get_project and from open_end_create_project.

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?

Gives an explicit trigger and two concrete example utterances for when to call it: resolving a project name the user mentioned earlier into an id. It does not name a competing alternative or state when not to use it, so it falls short of full routing guidance.

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