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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the returned field set and the underlying endpoint, but says nothing about pagination behavior or ordering, which matters for a list tool with page/per_page params.

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 tight sentence with the resource and payload front-loaded; the trailing endpoint reference is marginally redundant but not wasteful.

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 read-only list of two optional paging params with no output schema, the description covers what is returned and its safety profile is carried by annotations. Only pagination/ordering expectations are left implicit.

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 100% and both parameters carry their own defaults and limits, so the schema does the heavy lifting. The description adds no parameter semantics at all, making baseline 3 correct.

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 ('List all proposals') and enumerates the returned fields (name, status values, draft flag, dates), which gives an agent a clear picture of the payload. It does not explicitly distinguish itself from the sibling bidsketch_list_client_proposals, though 'all' implies scope.

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?

Usage is only implied: 'all proposals' suggests use this for an unfiltered listing rather than the client-scoped sibling, but no when-to-use or when-not statement is given. An agent must infer the choice between this and list_client_proposals.

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