analyze_collection

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

Annotations indicate readOnlyHint=false, but the description says only 'Analyze', which could imply a read-only operation. It does not disclose potential side effects, required state of the artifact, or any other behavioral traits. With no annotation-derived context, this is a significant gap.

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 concise and to the point, though it may be too terse to be useful.

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 the tool has an output schema and annotations, the description still does not convey what the analysis accomplishes, what outputs it produces, or how it fits with sibling tools. The low parameter count makes it simple, but the missing context leaves the agent guessing.

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 0%, so the description must compensate. It does not explain what collection_id refers to, how to obtain it, or what types are valid beyond the vague 'record/sched/lock/off-CPU' in the 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 uses the verb 'Analyze' with a specific resource 'stored record/sched/lock/off-CPU collection artifact', which is more than a tautology. However, it does not distinguish this tool from siblings like analyze_profile or analyze_benchmark, and the nature of the analysis is vague.

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?

There is no guidance on when to use this tool vs alternatives. The description does not mention prerequisites, competing tools, or situations where another tool would be more appropriate.

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