brc_get_accrual

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

No annotations provided. The description only discloses that child accruals are not returned, which adds minimal behavioral context. Missing details on idempotency, error states, or auth requirements—burden fully on description.

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 concise sentences. The first sentence delivers the core action and resource; the second adds a key limitation. No extraneous words.

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?

No output schema exists, yet the description does not specify what information is returned. It mentions 'information about' but is vague. For a get tool, more detail on response fields would improve completeness.

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 coverage is 100%, so both parameters (companyName, id) have descriptions in the schema. The description does not add extra meaning beyond what the schema provides, resulting in baseline score.

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 returns information about a single parent accrual by ID, and explicitly notes child accruals are not exposed, distinguishing it from list tools like brc_list_accruals.

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 implies when to use (retrieve a single parent accrual by ID) but lacks explicit comparison to siblings like brc_list_accruals (for multiple) or brc_create_accrual (for creation). The exclusion of child accruals provides some guidance.

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