sd_get_selection

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

The description adds 'bounded result size' beyond the annotations, hinting at the limit parameter. However, it does not elaborate on limit behavior, detail semantics, or response format. Annotations already cover read-only and idempotent aspects.

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, concise sentence with no filler. Every word contributes meaning, and the main idea is front-loaded.

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?

For a simple read tool with annotations and an output schema, the description is adequate but has a gap: the 'detail' parameter is not explained. It also doesn't clarify what 'selection' encompasses, but sibling context helps.

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 only mentions 'bounded result size' which relates to the limit parameter, but completely ignores the 'detail' parameter and its summary/full enum, leaving it unexplained.

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 the tool's function: reading the current graph node selection. It uses a specific verb ('Read') and resource ('current graph node selection'), and the 'selection' scope differentiates it from siblings like sd_get_node or sd_list_graph_nodes.

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 is provided on when to use this tool versus alternatives. There are no explicit 'use this when' or 'instead of' statements, nor any mention of prerequisites or contexts.

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