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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of each returned record (identifier, name, active flag, cost type) and the semantic definition of a cost code, which matters since there is no output schema. It omits response envelope details such as total counts and next_page.

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?

Two sentences, zero filler: the parenthetical definition comes first, the field list second, and the endpoint is appended. Nothing repeats the title or wastes a clause.

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?

For a simple, zero-required-parameter list endpoint with fully annotated params and read-only annotations, the description covers purpose, domain meaning, and returned fields. The one gap is the response envelope (paging metadata, totals), which the agent will only discover at call time.

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% and both parameters (page, page_size) carry their own ranges, defaults, and the useful 'pass the previous reply's next_page' instruction. The description adds nothing about pagination, 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+resource (list cost codes) plus a clarifying gloss that these are 'phases and work activities that time is booked against', which grounds the domain term. It also enumerates the returned fields and names the endpoint. It doesn't explicitly contrast with exaktime_get_cost_code, so a 4 rather than a 5.

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?

Usage is only implied: an agent can infer this is the bulk-enumeration path and get_cost_code is the single-record path, but the description never says so. There is no statement of when to prefer this over exaktime_query_odata or how to iterate pages, leaving the agent to infer behavior.

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