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

Annotations already declare readOnlyHint and idempotentHint, but the description adds significant context: it never starts analysis, settles credits, or applies proposals (reinforcing side-effect-free), requires visibility.read (auth), details pagination via supplying the returned run.id, and notes Slack execution is unsupported. This goes well beyond the annotations.

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?

The description is three concise sentences with no repetition. It front-loads the core purpose, then adds behavioral constraints and prerequisites. Every sentence contributes distinct information, making it efficient and well-structured.

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?

For a read-only tool with 3 optional parameters and no output schema, the description covers purpose, side effects, auth requirements, pagination, and environment limitations. An agent has enough information to call it correctly, including how to navigate subsequent pages via run.id.

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%, so the description must compensate for all parameters. It only mentions run.id for pagination and does not explain offset or pageSize at all. Since these are optional and self-explanatory as pagination controls, the lack of explicit guidance is a notable gap given the low coverage.

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 clearly states the tool reads project-scoped analysis state, assessments, proposals, and credit estimate/balance. It specifies the verb 'Read' and the resource, and explicitly distinguishes it from actions like starting analysis or applying proposals, separating it from sibling tools such as devtune_start_prompt_set_analysis.

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?

The description gives clear context: it is a free read, never starts analysis, settles credits, or applies proposals, implying when to use it for read-only needs. It also mentions requiring visibility.read and that Slack execution is unsupported. However, it does not name specific alternative tools, only implies them, so it lacks explicit when-not alternatives.

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