NTWX AAAS catalogue

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the domain limitation that it does not handle payment or quotes, which is useful context, but it does not describe what the tool returns or any other behavioral traits.

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?

Two short sentences with no filler, and the negative constraint is front-loaded after the purpose. It is appropriately sized for a no-parameter informational tool, though the first sentence is terse to the point of ambiguity.

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 output schema and no parameters, the description must carry the full burden of explaining what the agent gets back. It says only 'How to enquire' and a non-payment caveat, without describing the return content or how to use it, so it is incomplete for practical 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?

The tool has zero parameters and 100% schema description coverage, so there are no parameter semantics to explain. The baseline for a no-parameter tool 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 states the tool is about 'How to enquire' and excludes payment/quote actions, which conveys a vague purpose. It does not specify a verb+resource or distinguish itself from siblings get_catalogue and list_priority_surfaces.

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 only guidance is a negative: 'does not take payment or issue a quote.' That helps rule out financial use cases, but there is no explicit when-to-use nor named alternatives. The agent is left to infer that this tool is for enquiries generally.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's only added behavioral value is the hint that the result enumerates indexed items and named live URLs, but it says nothing about freshness, caching, or result size.

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?

It is a single short fragment with no wasted words, but the terseness tips into under-specification: the content is a noun clause rather than a complete, front-loaded statement of purpose, so brevity here trades away clarity.

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?

With no output schema and no structured return documentation, the description carries the full burden of explaining what an agent actually receives. It names two content types vaguely ('what it indexes', 'live URLs it names') but not the shape, enumerations, or limits of the response, nor how it relates to its siblings.

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 takes zero parameters with 100% schema coverage, so the schema fully documents the (empty) input contract. Per the baseline for parameterless tools, a 4 is appropriate; no parameter semantics need compensating in the description.

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 identifies the resource ('Parent NTWX catalogue') and gestures at its contents ('what aaas.ml-nightworx.io indexes, and the live URLs it names'), so an agent can infer this returns a catalogue. However it is a noun phrase rather than a clear verb+resource statement, and the jargon 'NTWX' is undefined, leaving the actual function somewhat opaque.

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 indication of when to call this versus alternatives. Neither sibling (engagement_path, list_priority_surfaces) is referenced, and no precondition or exclusion is given, so the agent must guess at the routing.

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

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that — no explanation of what 'priority order' means operationally or how stable the 'live' ordering is.

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?

It is a single short, front-loaded sentence with no waste, but its brevity comes at the cost of clarity rather than being genuinely concise.

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?

With no output schema and no parameters, the description carries the full burden of explaining what the agent receives. It does not describe the shape or meaning of the returned priority ordering, leaving the tool significantly under-specified.

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 takes zero parameters, so there are no parameter semantics to document; baseline 4 applies per the rubric.

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 phrasing 'Commander priority order for the live surfaces linked from AAAS' names a resource but no clear verb, and terms like 'Commander', 'surfaces', and 'AAAS' are undefined jargon. An agent cannot reliably tell what this tool returns or how it differs from engagement_path or get_catalogue.

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 indication of when to call this tool versus its siblings, no prerequisites, and no exclusion conditions. The agent is left to infer usage entirely.

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