instruments_list_templates

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

Without annotations, the description provides basic transparency by stating it lists all templates, but it does not disclose details like whether templates come from the system or user-defined, or if there are any side effects. The tool is simple, so the gap is minor.

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?

A single, front-loaded sentence efficiently communicates the tool's purpose without any unnecessary words or structure.

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 parameters and no output schema, the description is largely complete. It could mention whether the list is exhaustive or if templates are grouped, but the examples provided sufficiently convey the scope.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds value by naming example templates, which is helpful beyond the empty schema, earning a 5.

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 clearly states the tool lists available Instruments profiling templates and provides concrete examples like Time Profiler and SwiftUI, making the purpose specific and distinguishing it from sibling tools that start profiling sessions.

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 implicitly tells when to use the tool (when you need to know available templates). However, it does not explicitly mention when not to use it or suggest alternatives, such as instruments_list_instruments for listing instruments.

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