NTWX Studio catalogue

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and non-open-world behavior, so the safety profile is covered. The description adds the useful clarification that it does not book or charge, but it does not describe the return format or what kind of guidance it supplies.

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 two short sentences with no filler, front-loading the topic and then adding a clarifying limitation. It is concise but arguably under-specified rather than optimally sized for a tool with no output schema.

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 parameters and no output schema, the description should explain what the tool actually provides and when to use it. 'How to start a Block 0 brief' is not self-explanatory, and the description leaves an agent unsure what invoking it will return.

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 on the description. Baseline 4 is appropriate when no parameters exist.

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 says 'How to start a Block 0 brief,' which is a vague guide phrase rather than a specific verb+resource. It does not clarify what the tool actually returns or how it differs from sibling tools like get_source_of_truth or list_products.

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 implied use case is learning how to start a Block 0 brief, and the note that it 'does not book or charge' rules out a transactional purpose. However, there is no explicit when-to-use, when-not, or alternative tool guidance.

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, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that the catalogue is public and hosted at a specific URL; it does not disclose return behavior, pagination, or any other trait beyond annotations. No contradiction.

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 short sentence with no wasted words, but it is not front-loaded with a verb or clear outcome, and its brevity comes at the cost of useful selection detail.

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?

No output schema exists and the description does not explain what get_source_of_truth returns or how it relates to sibling tools. For a zero-parameter read tool, this leaves the agent without enough information to know when or why to call it.

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?

There are zero input parameters, so the description has no parameter semantics to add. Under the rules, a 0-param tool has a baseline of 4; no evidence supports raising or lowering it.

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 names a domain ('Operating layers for the public NTWX Studio catalogue at studio.ml-nightworx.io') but does not state an action or what the tool returns; it reads as a resource label rather than a definition for get_source_of_truth. It also does not distinguish this tool from siblings engagement_path or list_products.

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 when-to-use or when-not-to-use guidance is provided, and neither sibling is mentioned as an alternative. An agent gets no routing signal beyond the vague domain phrase.

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 adds one genuinely useful behavioral fact – that the AUD figures are indicative and not a quotation – which prevents an agent from treating the output as binding.

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 very short fragments with no wasted words. However, the most important information (that this lists products) is implied rather than front-loaded as a clear action.

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, so the description must carry the burden of describing returns. It partially does so (four products, AUD figures, indicative status) but omits what fields each product contains and how the set is scoped.

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 per the rubric the baseline is 4. Nothing in the schema needs compensating for, and the description introduces no parameter confusion.

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 (intelligence products with indicative AUD figures) but never states a verb like 'list' and leaves the odd count 'Four' unexplained. An agent can infer it returns a fixed set of products, but the phrasing reads more like a data caveat than a purpose statement.

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 the negative qualifier 'Not a quote,' which implies figures are indicative and non-binding. There is no statement of when to use this tool versus the siblings engagement_path or get_source_of_truth.

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