nexo_goal_profile_list

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

No annotations provided. Description only states 'currently available in the runtime', which is vague. Does not disclose whether listing affects state, requires permissions, or what 'available' means (e.g., active vs. archived).

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?

Single short sentence, but could include more details without becoming verbose. Lacks clarity on what a 'profile' is or how results are returned.

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?

No output schema, no annotations, and 3 undocumented parameters. Description fails to explain return format, filtering behavior, or what constitutes a 'profile'. Incomplete for safe invocation.

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 3 parameters with 0% description coverage. Description adds no meaning about parameters like scope_type, status, or limit. Agent must guess their semantics from names and defaults.

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 verb 'List', resource 'Goal Engine profiles', and context 'currently available in the runtime'. It distinguishes from sibling tools like nexo_goal_profile_get and nexo_goal_profile_set by specifying the listing action.

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. Does not mention scenarios or prerequisites for listing profiles, nor does it differentiate from other list tools like nexo_agent_list or nexo_goal_list.

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