set_company

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

Description describes a state-changing operation ('Switch... active company context'), contradicting the annotation readOnlyHint: true. This is a serious inconsistency that misleads the agent about the tool's safety profile. The description does not disclose other behavioral traits (e.g., permission requirements, side effects).

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?

Single sentence with no wasted words, efficiently conveying the action and a crucial validation tip. Perfectly front-loaded.

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 too brief for a tool that changes state, especially given the contradictory annotation. It does not explain the implications of switching context, return values, or error conditions. The validation tip is helpful, but the overall completeness is low due to the unresolved contradiction.

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 covers 100% of parameter descriptions, but the description adds value by instructing to validate the company name before use, which goes beyond the schema's 'Exact name' description. This helps the agent avoid errors.

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 states 'Switch TallyPrime's active company context' — a specific verb ('switch') and resource ('active company context'), clearly distinguishing it from sibling tools that mostly retrieve or create data (e.g., get_ledgers, create_ledger).

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?

Explicitly advises to validate the company name using get_ledgers, get_company_info, or the company list before calling, which is a clear pre-usage guideline. Does not mention when not to use, but the context of siblings makes the purpose obvious.

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