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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context beyond that: text is clipped to max_chars, clipping is signalled via clipped_fields/body_total_chars, and pagination is signalled via has_more/next_offset. Return-shape behavior is disclosed rather than left implicit.

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 tight sentences, no filler, with the core purpose front-loaded before the clipping and pagination caveats. Every clause carries operational information.

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?

There is no output schema, so the description carries the burden of explaining the return envelope (clipped_fields, body_total_chars, has_more, next_offset) and does so adequately. It could be slightly richer on what a 'problem' record contains, but combined with the 100%-covered schema it is complete enough to call correctly.

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 coverage is 100%, so baseline is 3, but the description adds cross-parameter workflow meaning the schema does not: offset should come from the previous page's next_offset, and max_chars clipping should be remedied with read_text. This connects parameters into an actual usage pattern.

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 (get) and resource (problem) and enumerates exactly what is returned: the problem, its comments, and the first page of solutions. The scope ('first page') is precise and an agent can distinguish it from list_solutions or list_open_problems.

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?

Explicitly routes the agent to alternatives under conditions: use read_text for clipped fields, use list_solutions with next_offset when has_more is true. It does not cover when-not-to-use (e.g., vs search_problems), but the continuation guidance is concrete and actionable.

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