observe

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

The description says 'Read', strongly implying a non-destructive read operation, but annotations declare readOnlyHint=false and destructiveHint=true. That is a direct contradiction, so the description fails to reliably disclose the tool's behavioral and safety profile.

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 a single, front-loaded sentence with no filler or repetition. Every clause identifies a resource that the tool reads.

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, and the description gives little detail about the shape or meaning of the returned state/tool/argument references. More importantly, its 'Read' framing conflicts with destructive annotations, so the definition is not complete enough for safe invocation decisions.

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 tool has zero parameters, so there is no parameter semantics burden. Baseline for zero-parameter tools is 4.

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 uses a specific verb ('Read') and names concrete resources: task state, currently available tools, and argument references. It is clear what the tool does, though it does not explicitly differentiate it from siblings such as 'arguments' or 'run_task'.

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 guidance on when to use this tool versus alternatives like 'arguments', 'operate', 'run_task', or 'read_report'. The description implies a read/observation role but gives no conditions, prerequisites, or exclusions.

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