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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: retain results in execution storage before displaying bounded portions, and do not transcribe installation bytes. It also notes workspace-only connection usability. No contradiction with annotations; the added storage/display guidance exceeds what annotations provide.

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, with the core purpose front-loaded and every sentence contributing operational detail. It is slightly dense but avoids filler; no wasted words. The length is appropriate for the complexity.

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 two optional parameters, no output schema, and annotations covering safety, the description covers the trigger, parameter usage, output handling, and scope. It lacks explicit return-format details, but the absence of an output schema makes that less critical. Overall, an agent has enough to call it correctly in the intended context.

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 100% and the schema already documents both parameters. The description enriches them: file's default and manifest path usage, and view's install mode returning an archive with hashes. This goes beyond the schema's basic descriptions, adding concrete operational meaning.

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 explicitly states it reads the Penny operating skill, names the trigger (stale/missing copy reported by session start), and distinguishes it from siblings by clarifying it is product guidance, not user-saved skills. This differentiates it from penny_read and other siblings without ambiguity.

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?

It provides a clear trigger condition (when session start reports stale/missing) and gives parameter-specific guidance (use file for manifest paths, view:install after approval). It implicitly excludes use for user-saved skills, but does not explicitly name alternative tools like penny_read, though the distinction is stated. This is strong but not exhaustive.

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