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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds no behavioral context beyond that — not the size/shape of the documentation returned, nor whether it is static reference material versus runtime state.

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?

It is a single short clause with no wasted words, but it is a topic list rather than a front-loaded statement of what the tool does. Brevity here comes at the cost of clarity, not from tight editing.

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?

With no parameters, no output schema, and a trivial surface, the description only needs to say what the agent gets back and when to call it. It partially covers the return content ('what Quarterline does, what happens to a request, the request fields') but omits any call-order guidance relative to submit_request.

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 takes zero parameters, so the baseline is 4. The phrase 'the request fields' gestures at what information is exposed, but there is no parameter to disambiguate.

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 title 'About Quarterline' plus the phrase 'What Quarterline does' signals an informational/onboarding tool, but the description never uses a verb like 'returns' or 'describes' and reads as a list of topics rather than a statement of purpose. It does not differentiate itself from submit_request or tell the agent what calling it produces.

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?

There is no when-to-use guidance at all — nothing says to call this before submit_request, nor any condition under which it should be skipped. The only hint is the fragment 'what happens to a request', which merely overlaps with the sibling's domain without routing the agent.

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