pad_list

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

With no annotations, the description shoulders the burden of behavior. It does disclose non-obvious behavior: pads are returned without full content, query searches names and content and returns a snippet, and tags match any listed tag. However, it does not mention pagination, default limit, project scope, or archived handling, leaving gaps for a six-parameter tool.

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 compact and front-loaded: the core purpose is in the first four words, and the filter semantics follow in a single sentence. There is no filler or repetition.

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 list tool with six optional parameters and no output schema, the description captures the central behavior and filter semantics. It omits return-shape details beyond 'snippet,' pagination behavior, and the project scope rule, so it is adequate but not 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?

Schema description coverage is only 17%, so the description must compensate. It adds meaningful semantics for query ('matches names and content... returns a snippet') and tags ('any listed tag'), but says nothing about limit, offset, include_archived, or project_id. The remaining parameter names are self-explanatory, but the coverage is incomplete.

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 starts with a clear verb and resource: 'List pads without full content,' which immediately distinguishes it from sibling pad_read (which presumably returns full content). It also explains the query and tag filters, leaving no ambiguity about what the tool does.

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?

No guidance is given on when to choose pad_list over pad_read or other pad tools; 'without full content' implies the distinction but does not name the alternative or state conditions. There are no exclusions, prerequisites, or 'use instead' cues.

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