get_parameter

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

The description states the tool is read-only ('without contacting the CPE', 'reads last-known values'), but the annotations set destructiveHint=true, which implies a destructive or modifying action. This is a direct contradiction between the description and the annotation, severely impacting transparency.

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?

Description is moderately concise and well-structured with clear sections. Some slight redundancy ('quickly retrieve') but overall efficient. Front-loaded with purpose.

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?

Covers purpose, usage, limitations, return format, and edge case (unread parameters not appearing). No output schema, but description sufficiently explains return. Could mention error handling or missing device, but overall complete for the tool's complexity.

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 100%, baseline 3. The description adds extra value by explaining comma-separated lists for parameter_path, providing concrete examples, and detailing the device_id format. This goes beyond the schema.

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?

Clearly states 'Read specific TR-069 parameter values from the GenieACS cache for a device without contacting the CPE.' The verb 'read' and resource 'TR-069 parameter values' are specific, and the mention of 'without contacting CPE' distinguishes it from refresh_parameter.

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?

Explicitly states when to use (quickly retrieve known values) and when not (if fresh value needed, use refresh_parameter). Provides practical examples and limitations, guiding the agent on appropriate context.

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