list_ksis

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

No annotations provided, so description carries full burden. Does not disclose behavioral traits such as pagination, read-only status, authentication requirements, rate limits, or mutation potential. Only states 'enumerate' without further details.

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?

Extremely concise: two sentences covering the purpose and parameter. No wasted words, front-loaded with the action and resource. Efficient for quick comprehension.

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?

Given no output schema and no annotations, the description fails to explain return structure (e.g., list of KSI objects, fields), pagination, or default behavior. Essential info for a list endpoint 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?

Adds meaning beyond the input schema (which only has type/name) by providing examples ('AFR', 'IAM', 'CMT') and clarifying the filter purpose. However, it lacks full enumeration or constraints, which would warrant a 5.

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?

Clearly states 'Enumerate FedRAMP 20x Key Security Indicators (KSIs)', which distinguishes it from the sibling 'get_ksi' (which retrieves a single KSI). However, it does not explicitly differentiate from 'list_frrs' or 'search', but the tool name implies a listing operation.

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?

No guidance on when to use this tool versus siblings like 'get_ksi' (single record retrieval) or 'search' (likely filtered query). Missing context about use cases or when not to use it.

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