plainweave_baseline_list

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

No annotations provided; description only states 'read-only'. Given the tool's simplicity (list with pagination), the description is minimally adequate but does not disclose potential errors, authentication needs, or any side effects beyond being read-only.

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 concise sentences with no extraneous information. The key points (operation, read-only) are front-loaded.

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?

Tool has a simple input schema (2 integer parameters, no enums) and an output schema exists, so return values need not be described. However, missing parameter descriptions and any mention of sorting or default behavior leave gaps.

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 0%. The description does not explain the purpose of limit and offset parameters, which are central to usage. The description fails to compensate for the lack of parameter documentation.

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 the verb 'List' and the resource 'local immutable Plainweave baselines', distinguishing it from sibling tools that perform other operations like diff, get, or search.

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?

Description implies a listing operation but does not explicitly differentiate when to use this tool vs plainweave_baseline_get for a single item. The 'read-only' note is helpful but lacks context for pagination or filtering.

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