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

With no annotations, the description carries the full disclosure burden. It states that the tool lists public SOPs and returns title and category, implying a read-only, likely authentication-free operation. It does not mention pagination, ordering, or any limits, but for a zero-parameter list operation the core behavior is reasonably clear.

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 a single sentence with no filler. It front-loads the verb and resource, then adds parenthetical detail about the returned fields, making it compact and easy to parse.

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 parameterless list operation with no output schema, the description is complete enough: it names the resource, the return fields, and the 'public' scope. An agent has everything necessary to invoke the tool correctly and understand what it will receive.

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 input schema is empty, so there are no parameter semantics to document. Per the baseline for zero parameters, the description is adequate; it adds useful context by naming the output fields, which is the only relevant semantic information.

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 uses the specific verb 'List' with a clear resource, 'Kanbai's public standard operating procedures', and even indicates the returned fields (title, category). This distinguishes it from sibling tools such as kanbai_get_sop and kanbai_list_templates by resource type and action.

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 usage is implied: an agent would call this tool when it needs a catalog of Kanbai SOPs. However, there is no explicit guidance about when to choose this over kanbai_list_templates or when to follow up with kanbai_get_sop, leaving sibling differentiation to inference.

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