Get setting

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

With no annotations, the description relies solely on the word 'Get' to imply read-only behavior, but no additional details about side effects, authentication, or return format are given.

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 very short (one sentence), which is concise but lacks structure and sufficient detail for a minimal viable description.

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 no output schema, no annotations, and a single parameter, the description fails to explain what the tool returns, what names are acceptable, or any side effects. It is insufficient 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?

The single required parameter 'name' is described only as 'by name', adding no meaning beyond the schema. The schema description coverage is 0%, and the description does not explain what values are valid or provide examples.

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 states it 'Get[s] a setting by name', which indicates the action and resource, but it does not differentiate from the sibling tool 'npm_get_settings' (which likely lists all settings) or clarify what a 'setting' is.

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 on when to use this tool versus alternatives like 'npm_get_settings' or 'npm_update_setting'. No prerequisites or context are provided.

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