get_bids_guide

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

No annotations are provided, so the description must carry the full burden of explaining what happens when the tool is called. It only says it is a 'Guide,' which suggests informational content, but it does not disclose whether the tool returns a text explanation, a link, a formatted document, or some other artifact. The behavioral profile is therefore largely opaque.

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, tightly worded sentence with no filler or redundancy. It front-loads the core topic ('BIDS') and the context ('in Flywheel'), making it immediately scannable for an agent.

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 zero-parameter informational tool, the description identifies the subject and scope adequately. However, with no annotations and no output schema, an agent still lacks clarity about what invoking the tool actually returns and how this guide differs from sibling documentation options. It is minimally viable but not complete.

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 input schema has no properties and no required parameters, so the description has no parameter semantics to explain. With zero parameters, the baseline score of 4 applies because there is no schema/description gap for parameter documentation.

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 identifies the tool as a guide to BIDS specifically within Flywheel, which distinguishes it from the sibling documentation tools that target different topics. However, it uses the noun 'Guide' rather than a strong action verb, so it is clear but slightly less definitive than a purpose statement like 'Returns documentation about BIDS usage in Flywheel.'

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 description implies when to use the tool: when the user needs guidance on using BIDS in Flywheel. It does not explicitly contrast this tool with sibling docs tools or state when not to use it, so the usage context is inferable but not directly articulated.

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