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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that this is a lookup endpoint (small, stable result set) and gives the raw path, but says nothing about result size, caching value, or paging behavior beyond the endpoint hint.

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?

Three short sentences: purpose first, downstream use second, technical endpoint last. Everything is load-bearing, though the raw GET path is of limited value to an agent that already has the tool bound.

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?

No output schema exists, but for a small lookup list the description conveys enough: what it returns (company payroll frequencies) and how the values are consumed. The only gap is that it doesn't describe the shape of returned items (code vs. name/id), which would matter for constructing the downstream `frequency` argument.

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%, with $top/$skip/$filter/$orderby and company_id already documented in detail. The description adds no parameter-level guidance (e.g. whether filtering is useful on a small lookup), so baseline 3 applies.

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?

Specific verb plus resource ('List the payroll frequencies of a company') with the underlying entity named (CompanyFrequency lookup) and the exact endpoint. It is clearly distinguishable from generic list siblings because it identifies itself as a lookup feeding a foreign-key argument.

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?

Explicitly states the downstream use: values go into the `frequency` argument of payspace_list_payroll_components, payspace_list_payroll_runs and payspace_list_recurring_components. It doesn't explicitly say 'call this first if you don't already have a frequency id', but the implication is strong and the alternatives are named.

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