get_pt5_samples

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

No annotations are provided, so the description carries full burden. It mentions retrieval and output units but does not disclose error behavior, performance implications, or whether it is read-only (implied by 'retrieve' but not explicit). The decimation hint is in the schema, not the description.

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 two sentences, immediately stating the core purpose and return values. Every word is functional, with no redundancy or unnecessary detail. It is well-structured and front-loaded.

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 5 parameters, no output schema, and no annotations, the description covers the purpose and key options but lacks details on return format (e.g., array, object), error handling, or limits. It is adequate for a straightforward tool but not comprehensive.

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%, providing good parameter descriptions. The tool description adds value by summarizing the optional filtering and decimation, and by stating the return units (mA, V), which are not in the schema. This enhances the agent's understanding beyond the schema alone.

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 retrieves sample data from a PT5 file with optional time range filtering and decimation, and specifies the return values (current and voltage). It distinguishes itself from sibling tools like get_pt5_header (metadata) and analyze_pt5_trend (analysis).

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 implies usage for raw data retrieval with filtering options but does not explicitly compare to siblings or state when to avoid using it. The context signals list sibling tools, but the description lacks direct guidance on alternative selection.

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