data_read_submatrix

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

The description's 'Read' is consistent with the readOnlyHint annotation, and 'bulk data access' adds a small behavioral nuance. The description does not go beyond this to mention rate limits, pagination behavior, or any other operational traits, but the annotation already covers the safety profile.

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 sentence with no filler. It front-loads the action and resource and immediately distinguishes the data access method. Every clause contributes to understanding.

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 readOnlyHint annotation and the presence of a full output schema plus 100% parameter schema coverage, the description does not need to re-explain returns or parameters. The definition is functionally complete for a read operation, though a brief note about when 'bulk data access' applies could have added a bit more context.

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%, so the input schema already documents all seven parameters with meaningful descriptions. The tool description adds no parameter-specific guidance beyond the general notion of reading a submatrix, so it does not exceed the schema baseline.

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 and resource ('Read timeseries data from a submatrix') and adds 'using bulk data access' to characterize the access mode. It is clear, but it does not explicitly distinguish this tool from siblings such as data_get_quantities or query_execute.

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 phrasing implies the tool should be used when reading timeseries data from a submatrix via bulk access, so the usage context is lightly implied. However, there is no explicit guidance about when to use this tool instead of sibling tools or any exclusions or prerequisites.

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