yaaif_session_files_list

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

With no annotations, the description carries the full burden. It does disclose the HTTP method (GET) and the latest_only behavior, which imply read-only operation. However, it does not explicitly state there are no side effects, nor mention pagination, permissions, or how results are ordered, leaving some behavioral aspects ambiguous.

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?

Two sentences with no filler. The main action is front-loaded, followed by the latest_only behavior and the sibling routing guidance. Each sentence earns its place.

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?

The tool has no annotations, no output schema, and sparse parameter documentation. The description omits essential context: what a 'session' is, how to obtain session_id, what limit does, and how results are shaped. This leaves significant gaps for correct invocation.

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 description coverage is 0%, so the description must compensate for all three parameters. It only explains latest_only; session_id and limit are left entirely unexplained. An agent cannot know what session_id refers to or what limit controls, making invocation risky.

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 action ('List session files') and the REST endpoint, then explicitly distinguishes from siblings by directing skill authoring to yaaif_files_list / yaaif_load_artifacts. This makes its role clear and prevents confusion with similar file-listing tools.

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?

Provides an explicit when-not by saying 'Prefer yaaif_files_list / yaaif_load_artifacts for skill authoring,' naming concrete alternatives. However, it does not state a positive condition for when to use this tool (e.g., 'when you need session-specific files'), so the positive use case is only implied by the name.

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