Create company (write)

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adding 'WRITE' is consistent but not additional. It does not disclose side effects, auth requirements, or behavior on duplicate names, which would add value beyond annotations.

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 a 'WRITE:' prefix front-loading the action. It is efficient but could include more detail without excessive length.

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?

For a creation tool with six parameters and no output schema, the description is too sparse. It lacks information on return values, error conditions, and usage context, making it incomplete for an AI agent to fully understand tool behavior.

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 67%, but the description only reiterates that name is required and others optional, adding no extra meaning about the six parameters. It fails to clarify the two undocumented parameters (callscore_enabled, keyword_spotting_enabled).

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 title 'Create company (write)' and description 'Create a new company in an account' clearly specify the verb and resource. The tool is distinct from siblings like update_company, delete_company, and list_companies.

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 states 'Requires a name; other fields optional', implying when to use the tool, but lacks guidance on when not to use it or alternatives. No explicit comparison to sibling tools.

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