agy_sessions

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

No annotations are supplied, so the description carries the disclosure burden alone. It does contribute one genuine behavioral fact, the default sort order (most recently used first), but says nothing about result capping/pagination or whether the operation is a safe read, which matters for a listing tool.

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 short sentences with the core action front-loaded and the ordering detail immediately after; no filler or restated title. A brief clause on the limit parameter would have been worth the extra words, but nothing present is wasted.

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?

An output schema exists, so return values need not be described, and the tool is a simple two-parameter lister. Still, for a tool with zero schema description coverage, the omission of the limit parameter's meaning and of any truncation behavior leaves an agent guessing about result volume.

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. It explains that 'cwd' means filtering by project, which does add meaning beyond the bare string-typed property, but the second parameter 'limit' (default 20) is never mentioned, leaving half the inputs unexplained in both schema and prose.

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 opens with a specific verb and resource ('List stored AGY sessions') and adds ordering ('most recently used first'), which separates it from siblings like agy_list_agents and agy_status. It stops short of explicitly naming a sibling or stating the scope of what a 'session' record contains, so it is clear but not fully differentiated.

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 only usage hint is 'Filter by project with cwd', which implies an optional narrowing case but gives no guidance on when to use this versus agy_status or agy_list_agents. There is no mention of the default result limit or what to do when more sessions exist than are returned.

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