update_firm

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

With no annotations, the description carries the full transparency burden. It correctly indicates a write operation and specifies that only passed fields change. For a simple tool, this is adequate. However, it lacks details on authorization, rate limits, or immediate effects, which would elevate it further.

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 succinct sentences with no extraneous information. The key instruction 'Only pass fields you want to change' is front-loaded. Every sentence earns its place.

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 4 parameters and no annotations, but an output schema exists, the description is minimally complete. It explains the partial update behavior but omits details like firm identification context or validation. It is adequate for a simple tool but could be more comprehensive.

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%, meaning no parameter descriptions in the schema. The description 'Update firm profile fields' does not add specific meaning beyond the parameter names (name, email, phone, address). While names are self-explanatory, the description should compensate more by explaining context or constraints for the parameters.

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 'Update firm profile fields' – a specific verb and resource. It also adds the partial update nuance with 'Only pass fields you want to change,' which distinguishes it from a full replacement. This clarity helps an agent know exactly what the tool does.

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 usage for partial updates but does not explicitly state when to use this tool over alternatives like 'get_firm' for reading or other 'update_*' tools for different entities. No when-not or alternative guidance is provided, only the partial update instruction.

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