ssh-session-policy-list

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

No annotations are provided, so the description must carry behavioral transparency. It correctly indicates a read-only operation by stating 'list', and specifies what is returned (inherited and session-level rules). However, it does not mention any potential side effects, permissions, or rate limits. The description is adequate but not thorough.

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 clear sentence with no extraneous information. It is appropriately front-loaded. A slightly longer description that includes usage guidance would still be concise.

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?

Without an output schema, the description provides a reasonable idea of return values (inherited and session-level custom policy rules). However, it does not clarify the structure of these rules, the scope of 'inherited', or how to interpret the list. Given the tool's simplicity, it is moderately complete but could be enhanced.

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% with a single optional parameter 'session' already described in the schema. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate.

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 it lists 'inherited and session-level custom policy rules' for an SSH session. The verb 'list' and resource 'policy rules' are specific, and it distinguishes from siblings like ssh-session-policy-upsert (create/update) and ssh-session-policy-remove (delete). However, it could more explicitly contrast with these 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?

The description implies usage to view active policies, but provides no explicit guidance on when to use this vs alternatives like ssh-session-policy-upsert or ssh-session-policy-remove. No when-not-to-use or prerequisite context is given.

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