Get Parameter Component

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

With readOnlyHint=true already declaring this as a safe read, the description adds useful behavior beyond annotations: it returns schema details and rowVersion, optional usage listing, and a meaningful precondition ('Requires project context'). It is consistent with the annotation and adds practical operational context.

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?

Two sentences carry all the essential information with no filler. The main purpose is front-loaded, and the optional parameter behavior plus prerequisite are compactly appended.

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 complete schema coverage and a readOnly annotation, the description is sufficient: it names the returned data, explains the optional usage flag, and states a prerequisite. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds extra semantic value by explaining the includeUsage parameter's effect and its recommended timing ('do that before deleting one'), which goes beyond the schema's simple default 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?

The description states a specific verb ('get'), a specific resource ('one reusable parameter component'), and the key returned content ('schema details and rowVersion'). It clearly distinguishes itself from list_parameter_components and sibling get_*_component tools.

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 provides clear usage context: use includeUsage to list referencing endpoints, and do so before deleting a component. It also notes the prerequisite of project context. It does not explicitly contrast with list_parameter_components, but the singular 'one' implies the appropriate use case.

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