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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly describes the returned content (statuses of proposals and member models), but it does not explicitly state that this is a read-only operation, nor does it mention any limitations like pagination or ordering. The description is adequate but lacks explicit safety or edge-case 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?

The description is a single, well-structured sentence that front-loads the action ('List') and the resource, followed by the specifics of what is included. Every word adds value, with no filler or redundancy.

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 parameterless list tool with no output schema, the description provides the essential return details: statuses of proposals and member models. It is reasonably complete, though it could mention that it returns only the authenticated user's proposals (already implied) or any pagination behavior. Given the simplicity, it suffices for an agent to call it correctly.

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 tool has zero parameters, and the schema coverage is 100% (trivially). With no parameters to document, the description does not need to add parameter meaning. The baseline for 0 parameters is 4, and the description does not introduce any ambiguity about input.

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 clearly states the tool lists the user's pack proposals along with status details (submitted/approved/rejected) and member model status. The verb 'List' plus the specific resource 'user's pack proposals' differentiates it from siblings like search_packs (which searches all packs) and get_pack (which fetches a single pack).

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 description provides no explicit guidance on when to use this tool versus alternatives. It does not mention that this is for the user's own proposals only, nor does it contrast with search_packs or my_assets. The usage context is only implied by the phrasing, leaving the agent to infer when to call it.

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