Get Block Settings

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

With no annotations, the description must carry the burden: 'Read' implies non-mutating and 'in a running session' hints at a runtime precondition, which is useful. It does not disclose failure behavior when the session is absent or stopped, nor how the default session is resolved, nor confirm the read-only profile explicitly.

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?

A single front-loaded sentence with no filler; the runtime scoping qualifier comes right after the core action. Nothing 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 no explanation, and the core action plus targeting are clear. The gaps are the unaddressed session_id semantics and the lack of any stated runtime precondition, which matter for a live-session read tool with no annotations.

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 0%, so the description must compensate. It helpfully clarifies that `block` is an instance name rather than a block type or ID, but `session_id` is never mentioned, so the meaning of defaulting to null (current/default session vs auto-resolve) is left undocumented in both schema and description.

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 verb and resource ('read the live settings of a block') plus scope ('in a running session'), which implicitly separates it from update_block_settings and from static metadata tools. It never names a sibling, so an agent must infer the contrast with describe_block or list_categories.

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?

'In a running session' implies the live-state context, but there is no explicit when-to-use versus describe_block (static info) or session_status, and no stated prerequisites such as needing an attached/active session. Usage is inferable rather than stated.

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