get_pending_proposals

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

No annotations provided, but description discloses sorting (most recent first) and output fields (agent slug, rationale, diff summary). Does not mention auth needs or rate limits, but for a read-only list tool with no parameters, this is adequate.

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 purpose, no wasted words. Efficiently conveys what the tool does and what the output contains.

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?

Given no parameters and existence of output schema, description covers purpose, sorting, and key output fields. Minor gap: does not specify scope (e.g., all pending proposals or only for current agent). Otherwise complete.

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?

Input schema has zero parameters with 100% schema coverage, so no parameter explanation needed. Description could explicitly state 'takes no parameters' but not necessary.

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?

Description clearly states 'List all skill improvement proposals awaiting review' with specific verb and resource, and distinguishes from sibling tools like propose_skill_improvement, approve_proposal, and reject_proposal.

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?

Implicitly indicates use for listing pending proposals, but no explicit when-to-use, when-not-to-use, or alternative tools mentioned. Agent could infer usage from context, but lacking explicit guidance.

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