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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so safety behavior is covered. The description adds useful context about which bill fields are returned, but it does not disclose ordering, pagination behavior, or rate limits.

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 very concise, but it is a sentence fragment and is under-specified for a list tool with filtering and pagination parameters. It front-loads returned fields, but lacks an actionable verb or usage structure.

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 field list provides useful information about returned data. However, the description omits filtering, pagination, and sibling-tool context, leaving the definition only minimally complete for a list operation with four optional parameters.

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 75%, with cursor, search, and project_id documented in the schema; only limit lacks a description. The tool description adds no parameter meaning beyond the schema, but because the schema already covers most parameters, this is near the baseline acceptable level.

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 identifies the resource (vendor bills) and enumerates returned fields, but it is a noun phrase rather than a clear action statement. It does not explicitly distinguish listing bills from getting a single bill or creating a bill, so purpose is inferable mainly from the tool name and title.

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 guidance on when to use this tool versus siblings such as get_bill, list_invoices, or create_bill. It also does not explain how or when to use search, project_id, or pagination.

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