check_project_billing_setup

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description indicates this is a read/audit operation and states the return type (list of rows with effective statuses), but it doesn't disclose whether all parameters are ANDed or ORed, whether omitting all filters returns everything, performance implications of cross-referencing multiple tables, or any required permissions. Given zero annotation coverage, this is thin.

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 multiline structure with a clear opening statement, a uses section, and a params/returns section is well-organized and reasonably concise. Every sentence adds value - the examples in the uses section are particularly helpful. It could be slightly tighter but is well-structured for its content.

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?

This is a moderately complex cross-referencing tool (projects × contracts × bill plans × statuses) with no output schema and no annotations. The description covers the input semantics and return shape at a high level, but given the tool's complexity and the presence of sibling tools with overlapping concerns (get_bill_plan, get_project_contracts), it doesn't fully clarify how results aggregate or how filters narrow the result set.

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 0%, so the description must compensate. It lists the three parameters with brief inline examples ('UCD', 'UCB' for business_unit) but doesn't explain how filters compose (are they combined with AND?), whether they're mutually exclusive, or how to specify a project (ID format). The parameter names themselves are self-explanatory, but the description adds minimal meaning beyond their names.

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 clearly states the tool checks how projects are set up for billing, enumerating the specific elements examined (contract lines, bill plan, bill plan type, effective statuses). It's specific about the resource (projects' billing setup) and gives concrete examples for what it's used for, though it doesn't explicitly distinguish from siblings like get_bill_plan or get_project_contracts.

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 description gives an explicit when-to-use purpose: 'Use this to spot setup problems' with concrete examples (active project tied to inactive bill plan, contract line with no bill plan). It doesn't explicitly state when NOT to use alternatives, but the diagnostic/audit framing differentiates it from the more targeted sibling tools like get_bill_plan.

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