get_goals

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

With no annotations, the description should disclose behavioral traits. It only mentions 'cleaned data in TOON format' which hints at transformation but lacks specifics on safety (destructive?), authentication, rate limits, or pagination behavior despite cursor parameters.

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?

Extremely concise (one sentence) but under-specified. It omits critical details like what 'TOON format' is, why data is cleaned, and how to use parameters. Conciseness should not come at the expense of completeness.

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 8 parameters, no output schema, and no annotations, the description is insufficiently complete. It fails to explain return structure, pagination, or filtering semantics, leaving the agent with only parameter names and types.

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?

Input schema has 100% description coverage for all 8 parameters, so baseline is 3. The description adds no additional meaning beyond the schema; the 'cleaned data' comment is about output not 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?

Description clearly states 'Get maker goals' which establishes the resource and action. However, it does not differentiate from sibling tool 'get_goal' which likely retrieves a single goal, nor from other list tools. The mention of 'TOON format' is unique but unexplained.

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?

No guidance on when to use this tool versus alternatives like get_goal, search_posts, or other get_* tools. No mention of context such as user or workspace filtering despite having parameters for userId and makerGroupId.

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