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

The annotation declares readOnlyHint: true, and the description repeats 'Read-only'. This is consistent and adds no contradiction. However, beyond that, the description does not disclose additional behavioral traits such as pagination, error handling, or rate limits. Given the annotation covers the safety profile, a score of 3 is appropriate.

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 with no superfluous words. The first sentence conveys the purpose and examples, the second confirms idempotency. Highly efficient.

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 output schema, the description lists example metrics, which helps the agent anticipate return values. It also specifies that the ticker must be exact. It does not mention result ordering or pagination limits (though limit parameter exists), but overall it is complete enough for a read-only data retrieval tool.

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%, so the schema already documents all parameters. The description lists example values for ticker, category, and metricKey but does not add significant meaning beyond the schema. The baseline of 3 is correct.

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 fetches operating KPIs and unit-economics metrics for a specific ticker, listing concrete examples like ARR, NRR, RPO. This distinguishes it from sibling tools that handle financial history, transcripts, etc.

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 says 'for one exact Bullrun ticker', implying a required ticker. It provides context about period-specific KPIs but does not explicitly state when to use this tool vs. alternatives like get_financial_history or get_forward_estimates. However, the examples differentiate it sufficiently.

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