cms_bdlaws_act

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

No annotations are present, so the description must carry the full burden. It discloses the tool is read-only ('Return'), the data source (bdlaws.minlaw.gov.bd), and the scope (20 acts). However, it omits behavioral details such as authentication requirements, rate limits, data freshness, or whether it returns a single result or multiple matches.

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 a single sentence with no wasted words. The main action and key constraints are front-loaded, achieving maximum information density in minimal space.

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 the tool's simplicity (one optional parameter, no output schema), the description adequately covers what it returns and its scope. It could mention whether the return is a list or single object, but overall it provides enough context for correct invocation.

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?

The schema covers 100% of the single optional parameter with a description. The description adds context by framing the filter within the '20 registered core business/corporate acts' and provides concrete examples, enhancing the semantic value beyond the schema alone.

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?

Description clearly states the verb 'Return' and the specific resource: 'official Bangladesh law link and metadata for the 20 registered core business/corporate acts'. It distinguishes from sibling tools by being uniquely focused on Bangladeshi statutory laws and a fixed set of 20 acts.

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 'Tier 2 mandatory statutory floor' implies a regulatory context, but the description does not explicitly state when to use this tool versus siblings like cms_search_policy or cms_risk_lookup. No when-not or alternative guidance is provided.

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