session_show_defaults

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

With no annotations provided, the description carries the full burden. It discloses the tool is a read operation (no side effects), but doesn't mention whether defaults are session-scoped or what happens if no defaults are set. The description is adequate for a straightforward query 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?

The description is a single sentence, perfectly focused, and front-loads the purpose. Every word adds value, with no redundancy or unnecessary detail.

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 0 parameters, no output schema, and no annotations, the tool is simple. The description clarifies the source of defaults (session_set_defaults), which is complete enough for selecting this tool among 77 siblings.

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 100%, but with 0 parameters, the schema is inherently complete. The description doesn't list parameters (none needed), so it adds no parameter info, but the baseline for 0-param tools is 4 as no compensation is required.

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 'show' paired with the resource 'project_dir/serial defaults pinned for this session', clearly distinguishing it from sibling tools like session_set_defaults and session_clear_defaults. It precisely identifies what the tool returns (pinned defaults).

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 explicitly clarifies that defaults are those set via session_set_defaults, which implies a complementary relationship to that sibling. It doesn't state when not to use it or provide explicit exclusions, but the context makes usage clear.

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