taxcredit-engine__get_rule_pack

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only mentions the return type but omits side effects (likely none), authentication needs, rate limits, or any constraints. The brief phrase does not adequately inform the agent of behavioral traits.

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, which is concise. However, it packs domain context (credit types) in brackets, which could be separated for readability. Still, it is front-loaded and efficient with no wasted 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?

Given the tool has one parameter with no schema description, no output schema, and no annotations, the description is too brief. It fails to explain what a 'rule pack' is, what metadata is returned, the format of the response, or how to use the credit parameter. The agent is left with significant unknowns.

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%, and the description does not explain the 'credit' parameter beyond its name. The credit types listed in brackets are context for the tool's domain, not parameter guidance. The agent receives no help on what values are valid or how to format the input.

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 states a specific verb ('Return'), a clear resource ('bundled rules and official source metadata'), and scopes it to 'one credit'. It also lists the relevant credit types in brackets, providing context. This distinguishes it from sibling tools like 'list_rule_packs' which presumably lists all packs.

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?

No guidance on when to use this tool versus alternatives (e.g., 'list_rule_packs' for browsing, or 'calculate_tax_credit' for computation). No prerequisites or context for appropriate use are mentioned.

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