List proposals awaiting the principal

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the queue contains unconfirmed lessons for confirmation, revision, or rejection, but omits return format, pagination, and authentication context.

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?

It is a single, short phrase with no wasted words. It is front-loaded with the resource, though it is a sentence fragment rather than a structured description.

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 queue with no output schema, the description gives the essential return content ('unconfirmed lessons'). However, it does not compensate for the undocumented workflow parameter and provides no additional behavioral context beyond what annotations already cover.

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 one optional parameter, 'workflow', with 0% description coverage, and the description does not mention it at all. An agent gets no explanation of what the workflow filter does or how omitting it behaves.

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 a clear resource and state: 'Unconfirmed lessons' awaiting the principal. It does not state an explicit verb like 'list' and does not differentiate itself from siblings such as twin_approval_status or twin_search, but the purpose is still clear from the noun phrase.

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 phrase 'to present to the principal' implies the use case—gathering items before a principal review—but there is no explicit when-to-use guidance, prerequisites, or comparison to alternative sibling tools. Usage is inferable rather than stated.

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