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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real context beyond that: what each mode returns (the full skill, keyword matches, or a name-and-description listing) and that a skill is instructions the agent is expected to follow. It doesn't cover pagination or return size, keeping it just short of 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?

Four sentences, zero waste, front-loaded with the core verb+resource before the usage modes. Each sentence carries a distinct payload: definition, example, parameter routing, and the recall directive.

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 annotations covering safety and no output schema, the description fully compensates by explaining what is returned in each of the three modes and when the agent should reach for the tool. Nothing needed to call it correctly is missing.

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%, so the baseline is 3, but the description goes further by tying each parameter to a distinct behavior mode and providing a concrete example id ('docfarm/onboarding') plus the id-is-array case. This adds selection semantics beyond the field-level text.

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 (Load) and resource (Docfarm skill) and immediately defines what a skill is: 'written instructions for a task that you then follow.' No sibling tool touches skills, so it is unmistakable in the toolset.

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?

Explicitly maps every invocation mode: 'id' for the full skill, 'query' to search by keyword, or nothing to list everything, plus the routing rule 'When the person asks to use a Docfarm skill by name, call this with that id first.' The agent knows exactly which parameter to pass for which situation.

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