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

No annotations exist, so the description carries the full burden. It does useful work by declaring the operation read-only, mentioning cursor pagination, decoding the unscored_reason value, and flagging *_untrusted/Commons content as data rather than instructions. It still omits auth/scope behavior, default and maximum page sizes, and ordering of results.

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?

Three compact sentences, front-loaded with the core purpose and followed by the semantic footnote and safety warning. Dense but every clause adds information; the only weakness is that the safety note reads as a run-on.

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 annotations, no output schema, and zero schema coverage on five parameters, the description should explain at least filtering and paging semantics. It covers purpose, one output field's meaning, and a prompt-injection warning, but leaves the agent guessing about since/status/question_id behavior and result ordering.

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 five parameters, so the description must compensate and largely does not. Only "cursor" is explained via the pagination phrase; limit, since, status, and question_id get no meaning, format, or default from the description.

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?

States a specific verb and resource ("Read ... my own forecasts") and enumerates what is returned: private rationale and scoring, with cursor pagination. The scoping word "my own" implicitly separates it from list_questions/get_question, but no sibling is named explicitly.

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 when-to-use guidance: nothing says when to prefer this over get_question, list_questions, or ledger_similar, and no prerequisites or exclusions are given. Usage is only inferable from the possessive "my own forecasts".

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