Stream Ingress

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

Annotations indicate readOnlyHint=false, suggesting side effects, but the description implies a read operation without clarifying. The description adds minimal behavioral context beyond annotations, such as the 'Real-time Streaming' group, but fails to explain streaming behavior or potential side effects.

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 with two short lines plus an example. It is front-loaded with the main action, but the group line adds minimal value and could be integrated. Overall, it is efficient but lacks structured parameter documentation.

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 simple one-parameter tool without an output schema, the description is adequate but incomplete. It does not explain what a 'sign-ingress' is, describe the output format, or differentiate from similar tools. The example helps but leaves gaps.

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?

With 0% schema description coverage, the description must compensate. It only provides an example ('days':30), which implies the parameter's purpose but does not explicitly describe it, its format, range, or default value.

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 it returns 'next planet sign-ingresses for N days,' providing a specific verb and resource. However, it does not differentiate from the sibling tool 'ingresses' or other streaming tools, limiting clarity.

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?

No guidance is given on when to use this tool versus alternatives like 'ingresses' or other stream tools. An example request body is provided, but it lacks context on appropriate usage scenarios.

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