discover_profile

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

Annotations provide readOnlyHint=false and destructiveHint=false, and the description adds that the tool refreshes state and invalidates stale diagnostic results. This clarifies the mutation side effect and does not contradict the annotations.

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, front-loaded sentence with no filler. It is appropriately sized for a one-parameter tool, though it is somewhat terse.

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?

With an output schema and full parameter coverage, the description doesn't need to explain return values or parameters. However, it omits prerequisites, when refreshing is valid, and how invalidation affects the diagnosis workflow.

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 100%; diagnosis_id is already documented as 'Identifier returned by start_diagnosis.' The description adds no additional parameter detail, so the baseline 3 applies.

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 identifies a specific action ('Refresh'), a target resource ('dynamic dependency profile'), and a consequence ('invalidate stale diagnostic results'). It distinguishes this from siblings like start_diagnosis or get_diagnosis, though it doesn't define what the profile 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?

The phrase 'invalidate stale diagnostic results' implies usage when prior diagnostics may be stale, and 'Refresh' suggests a maintenance/update action. However, it does not explicitly name alternatives or state when not to use this tool, leaving the agent to infer the trigger.

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