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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds provenance context (goals are set by vote on Trana, spanning people and agents), but says nothing about ordering, pagination, or how many goals are returned, and the trailing ellipsis leaves it visibly incomplete.

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?

Short, but short because it is a truncated fragment rather than a tight sentence; the trailing '...' signals missing content. It is not structured to front-load the operation, only the subject.

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 exists and the description does not describe the return shape, list semantics, or the one parameter. For a read tool with zero schema documentation coverage, this leaves the agent without enough to invoke it confidently.

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 0% and the sole parameter (limit) is undocumented. The description never mentions the limit parameter, so it fails to compensate for the schema gap — the agent cannot tell whether limit caps goals returned or is required for correct behavior.

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 description identifies the resource — the swarm-wide goals decided by vote on Trana — which distinguishes it somewhat from the sibling goal_tasks. However, it is a noun phrase fragment ending in an ellipsis, with no verb indicating that the tool retrieves or lists these goals, so the actual operation stays implicit.

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?

There is no statement of when to call this versus goal_tasks, tasks_open, or trana_proposals, all of which touch adjacent concepts. The agent must infer usage from the resource name alone.

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