Read the core SFL Skill or one bundled reference

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: no Library setup required, no Skill installation, and no helper code execution. No contradiction exists.

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 three short sentences with no filler. The most important guidance is front-loaded with 'Start here,' and each sentence provides relevant, non-redundant information.

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 read-only retrieval tool with one optional parameter, the description covers the purpose, return value, setup expectations, and side-effect boundaries. The only gap is the ambiguity about where 'listed document IDs' are found, but this is minor for an entry-point tool.

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 single parameter has no schema description, and schema coverage is 0%. The description partially compensates by indicating the document parameter selects the bundled SKILL.md or a listed bundled reference, but it does not explain how the document IDs are listed or the exact accepted values.

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 clearly states the tool returns the bundled SKILL.md and serves as the starting point for SFL guidance and host capabilities. It distinguishes itself from siblings by noting that no Library setup is required and that it does not install or execute code.

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 explicitly says 'Start here' and restricts on-demand usage to listed document IDs. It also clarifies what the tool does not do, but it does not name specific alternative tools for installation or execution scenarios.

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