manage_company_profile

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

No annotations; description explains update behavior for save (same ID updates) and revenue format (natural language). Lacks details on authentication, error handling, or idempotency for delete/list.

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?

Structured with action list and revenue note. Concise with minimal fluff. Could be slightly more condensed but effective.

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?

Output schema exists, so return values not needed. Covers basic usage but lacks details on list output format, error cases, or edge conditions for a CRUD tool.

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% description coverage; description explains action enum, profile_id/name requirement for save, and revenue format. But other params (licenses, certifications, prior_contracts, notes) are undocumented.

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 clearly states it manages company profiles for suitability evaluation, listing actions (save, load, list, delete). Distinct from sibling tools like analyze_competitor or score_bid_fit.

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?

Context is clear: used for company profile CRUD in evaluation. Action list with required parameters guides usage, but no explicit when-not-to-use or alternatives mentioned.

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