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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds important context beyond that: no Replo account is required, listing returns names and descriptions, loading returns full SKILL.md content, and bundled files are read by skill directory plus relative path.

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 front-loaded around what skills are and the primary workflow, then moves to file reading and auth independence. Every sentence contributes operational guidance.

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?

There is no output schema, but the description explains the return shape for both modes: a list of skill names/descriptions, a full SKILL.md, and bundled file paths. Combined with annotations and the fully documented parameter, it is complete enough for an agent to invoke correctly.

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 schema already explains the optional name parameter, including the list-vs-load behavior and file-path example. The description reinforces those semantics but does not add substantial meaning beyond the structured 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?

The description states a specific resource and action: Replo skills documentation, with two modes (list all skills, or load one skill's full SKILL.md). It also explains that skills bundle files by relative path, so an agent can distinguish this documentation-retrieval tool from the many operational siblings.

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 gives clear usage context: call before doing Replo work, list first, then load by name, and it can be used without a Replo account before asking the user to sign in. It does not name explicit exclusions or alternative sibling tools, which keeps it just below the top score.

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