analysis.progress

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

No annotations are present, so the description should inform about behavioral aspects like blocking/non-blocking behavior, whether it mutates state, or if it requires specific permissions. The description is too brief and provides none of this context.

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 concise at five words, which is appropriate for a simple tool. It is front-loaded with the action, but could include more detail without being verbose.

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?

Given the lack of output schema and annotations, the description should cover expected output (e.g., progress percentage, status fields) and prerequisites (e.g., session must exist). The current description is insufficient for an agent to use the tool correctly without additional context.

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?

The schema has only one parameter ('session_id') with no description, and schema description coverage is 0%. The tool description does not explain what 'session_id' represents (e.g., identifier of an analysis session) or how to obtain it, failing to add meaning beyond the schema.

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 'Get analysis progress snapshot' states a clear verb 'Get' and resource 'analysis progress snapshot', providing a basic understanding of its purpose. However, it does not differentiate it from sibling tools like 'analysis.status', which likely has a similar function.

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 does not provide any guidance on when to use this tool versus alternatives such as 'analysis.status' or 'analysis.update'. There is no mention of prerequisites (e.g., session must be active) or when it is appropriate to invoke this tool.

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