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

With no annotations, the description carries the burden. It notes that data is based on 'each company’s latest financial report,' which is useful behavioral context. However, it does not disclose potential response size, rate limits, or any other operational side effects, leaving room for surprises with a bulk operation.

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 concise, two sentences, with the core purpose front-loaded in the first sentence. The second sentence adds value about the data content without fluff or redundancy. Every sentence earns its place.

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 that there is no output schema, the description should clarify what the response looks like. It only states 'critical financial ratios and metrics,' which is vague and does not enumerate specific fields or the response format. For a bulk tool, an agent might need to know more about the data structure to use it effectively, so the information is incomplete.

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?

The tool has zero parameters, and the schema coverage is 100%, so there are no parameter details to explain. According to the rubric, a baseline of 4 is appropriate when no parameters exist, and the description does not need to add parameter semantics.

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's function: 'retrieve trailing twelve months (TTM) data for all companies available in the database.' This distinguishes it from single-company tools like getKeyMetricsTTM by explicitly noting the bulk scope for all companies, with a specific verb and resource.

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 when bulk TTM data for all companies is needed, but it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or refer to sibling tools. Guidance is absent beyond the implied scope.

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