list_pinned_tasks

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

Despite no annotations, the description thoroughly discloses behavior: it returns a JSON array with specific structure, reconciles inconsistencies by dropping unpinned/deleted entries, and guarantees self-consistent output safe for rendering. No contradictions.

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 extremely concise (about 60 words) and front-loaded. The first sentence states the core purpose, the second adds output details and behavioral guarantees. Every sentence earns its place with no wasted words.

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 zero parameters and an output schema (inferred), the description fully covers the tool's behavior including reconciliation logic and output format. No gaps remain for an agent to understand invocation or results.

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 input schema has zero parameters, so the description does not need to add parameter details. Baseline 4 is appropriate as the schema coverage is 100% and no parameters exist to clarify.

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 uses a specific verb 'List' and clearly identifies the resource as 'sidebar-pinned items in display order'. It distinguishes this tool from siblings like 'set_item_pinned' and 'reorder_pinned_tasks' by focusing on listing, not pinning or reordering.

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 clearly states the tool's purpose (listing pinned items in order) and implies usage in sidebar rendering context. However, it does not explicitly state when not to use this tool or provide alternatives for other listing needs.

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