get_act_text

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

Discloses that it returns R2 CDN URLs and that content must be fetched from those URLs. Also mentions cost. No annotations provided, so description carries burden.

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?

Three sentences, front-loaded with purpose, no unnecessary 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?

Simple tool with one parameter; description covers purpose, parameter example, return behavior, and cost. Output schema handles return values.

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 has 0% coverage, but description adds meaning by giving example act_id format and explaining what it represents (e.g., ‘IND_central_2187’ for Indian Contract Act).

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 it gets URLs for full text, PDF, and HTML versions of Indian acts. It distinguishes from siblings like get_us_statute_section_text which returns text directly.

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?

Provides example act_id and mentions cost, implying when to use. Does not explicitly contrast with alternatives but context hints at Indian act focus.

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