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

Annotations already declare readOnly, non-destructive, open-world, and the description is consistent with them. It goes further by disclosing the auth scope and the pagination contract (next_offset must be passed back as offset), which the agent cannot infer from annotations. It stops short of describing rate limits or result ordering defaults.

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?

Four short sentences, nothing wasted, and the scope plus endpoint come before the return-shape note. The telegraphic fragments ("GET /reporting/projects.") are compact rather than confusing.

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 output schema, the description correctly spends its words on the response shape (count, total, next_offset, items) and how to page. Given 100%-covered parameters and existing annotations, what remains missing is minor.

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%, so baseline is 3; the six parameters including the filter DSL and sort syntax are already fully documented in the schema. The description only reinforces the offset/next_offset loop, which the schema itself also states.

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?

States a specific verb and resource ("List projects") and adds the endpoint GET /reporting/projects, so an agent knows exactly what it retrieves. It is distinguishable from the singular smallinvoice_get_project by name, though the description never says so explicitly.

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 required "project" scope is a useful prerequisite that tells the agent whether it can call at all. However, there is no guidance on when to prefer this list over smallinvoice_get_project, nor any mention of conditions or exclusions.

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