get_collection_priority

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

The description indicates it returns read-only evidence, so side effects are not impliedasi. No annotations are present, but as a getter, the behavior is somewhat inferable. It does not specify errors, auth, or configuration dependencies.

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?

A single precise sentence with no filler. It conveys the operation, target, and scope efficiently.

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?

The description is adequate for a simple getter and the output schema exists, but it lacks usage guidance, alternatives, and explanation of what 'configured collection score evidence' actually contains.

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?

Even though the parameter schema is only a raw string, the description ties the operation to 'one synthetic invoice', which effectively identifies the invoice_id parameter and explains its scope.

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?

Clearly states the operation ('Return'), the resource ('configured collection score evidence'), and the scope ('for one synthetic invoice'). This distinguishes it from the sibling tools, which target implementation summaries and payment investigation.

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 phrase 'for one synthetic invoice' gives a clear invocation context. However, it does not explicitly describe when to choose this tool over the sibling tools or mention any exclusions.

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