goals_create

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

No annotations provided, so description carries full burden. Mentions that a report is automatically created to track progress. Lacks disclosure of error conditions, idempotency, or permission requirements.

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?

Concise with three clear sections: intro, workflow tips, use cases. Efficiently conveys how to use the tool, though slightly repetitive in examples. Front-loaded with the core purpose.

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?

Covers key creation aspects and provides examples, but lacks information on return values (e.g., created goal ID) and error handling. Given no output schema, description should address what the tool returns.

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 coverage is 100% with descriptions for all properties. Description adds value by providing workflow tips and concrete examples (e.g., type 'deals_won' with tracking_metric 'sum'), making parameter usage clearer.

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 'Add a new goal to track performance metrics' and enumerates the components (type, assignee, expected outcome, duration). It distinguishes from sibling goal tools (goals_list, goals_update, goals_delete) by focusing on creation.

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?

Provides workflow tips and common use cases with examples (e.g., track deal revenue, activities, team goals). Does not explicitly state when not to use this tool or compare with alternatives like deals_create or activities_create.

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