fabric_list_notebooks

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

The annotation already indicates readOnlyHint=true, so the description adds little beyond the workspace scope. No details on pagination, ordering, limits, or error behavior are given. The description does not contradict annotations.

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 concise sentence with no extraneous information. Every word is necessary and front-loaded.

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?

Given the tool's simplicity (one optional param, no output schema), the description is minimally adequate. However, it lacks information about return value structure or pagination, which would be helpful for an agent to use correctly. The annotation partially compensates for safety, but completeness for selection/invocation is mediocre.

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 coverage is 100%, and the description provides no additional parameter semantics beyond the schema's 'Workspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)'. The minimal description does not compensate for missing details like parameter format or validation.

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 the tool lists notebooks in a workspace. The verb 'List' and resource 'notebooks' are specific, and the name itself distinguishes this from sibling list tools (e.g., fabric_list_items) by narrowing to notebooks. However, it does not explicitly contrast with fabric_list_items which could also list notebooks.

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 provided on when to use this tool versus alternatives like fabric_list_items or fabric_get_notebook. The description lacks context about appropriate use cases, edge cases, or prerequisites (e.g., workspace existence).

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