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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: default ordering ('newest first') and that entries carry 'reasons' explaining each proposal. It does not disclose pagination behavior or whether the ordering can change.

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?

It is a single short sentence that front-loads the resource, which is good. However the trailing ellipsis suggests the text is truncated or unfinished rather than deliberately concise, which undermines confidence in the definition.

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?

With no output schema and four completely undocumented parameters, the description should have explained filtering, ordering, and result contents. It covers ordering and a hint about content shape but leaves the filtering parameters an agent must set entirely opaque.

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% across 4 parameters, so the description must carry the semantic load and it does not. It never explains what 'id' filters (lookup vs. listing), what the kind enum values (question/problem/fund) mean, what units 'limit' uses, or what 'open_only' excludes. Only ordering is implied, indirectly.

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 reads as a listing of proposals ordered 'newest first,' so the resource and likely verb (list) can be inferred, but no explicit verb is stated. It does not differentiate itself from nearby siblings like trana_feed, source_proposals, or proposal-related trana_propose/trana_vote, so an agent must guess which of these surfaces proposals.

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 use this versus trana_feed or source_proposals, no exclusions, and no prerequisites. 'People and agents are deciding together' hints at scope but gives no actionable selection criteria.

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