get_top_scheduler_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, whether it triggers a cook, what happens if the node_path is invalid, or what information is actually returned. The phrase 'Get information' implies a read, but the description does not disclose any side effects or edge-case behavior.

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 short and front-loaded with the core purpose, which is good. However, the 'Args:' block is mostly redundant with the input schema and does not earn its place; it adds no semantic value beyond restating the parameter name.

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 tool with no annotations, no output schema, and a single parameter, the description should explain what 'TOP scheduler info' means, what kind of data is returned, and any prerequisites. It does none of that. The sibling list shows many related TOP tools, and this description does not position itself among them, leaving an agent under-informed for correct invocation.

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%, and the description only repeats the parameter name 'node_path' with a vague gloss ('TOP scheduler or TOPnet path'). It does not explain what a TOP scheduler path looks like, whether it must be an absolute path, or how it differs from a regular TOP node path. The description adds minimal meaning beyond the schema's bare property name.

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 states a specific verb and resource ('Get information about TOP scheduler nodes in a network'), which is clear enough to identify the tool's basic purpose. However, it does not distinguish this from the closely related sibling get_top_network_info or other TOP tools like get_pdg_graph, so an agent cannot tell exactly what makes this tool unique.

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 such as get_top_network_info, get_pdg_graph, or get_work_item_info. The description only says what it does, not when it should be selected, so an agent has to infer usage from the name and sibling list.

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