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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavior beyond the schema: a 100-item cap per call, newest-first ordering, and offset-based paging. It does not describe the shape of returned items, which keeps it from a 5.

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?

A single front-loaded sentence packs the verb, resource, scope, sort order, page size, and paging instruction with zero filler. Nothing wasted, nothing buried.

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?

With no output schema, the description must carry return behavior, and it usefully documents page size, ordering, and the paging signal (a full page means more may exist). Minor gap: it doesn't hint at the fields a skill entry contains, but for a simple list tool the definition is largely sufficient.

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 coverage is 67%, with offset and workspace_id documented in-schema but path left bare. The description compensates by defining path as "workspace-relative" and explaining the paging contract ("at most 100 per call; pass offset for the next page"), adding meaning beyond the raw schema.

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?

States a specific verb and resource ("List the skills") plus scope ("saved under a workspace-relative path in the connected Pathrule workspace") and ordering (newest first). This cleanly distinguishes it from sibling list tools such as pathrule_list_memories and pathrule_list_rules.

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 makes the tool's context clear (enumerating skills under a path) and notes it is read-only, but never says when to prefer it over alternatives like pathrule_get_context or pathrule_read_skill, nor any exclusions. Usage is implied rather than prescribed.

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