local_workboard_config

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the return value and usage condition, with no mention of side effects, error behavior, permissions, or whether the call is read-only. This is insufficient for a tool with no other behavioral indicators.

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, front-loaded sentence with no extraneous information. It is efficient for conveying the core purpose, but could be slightly improved by including a brief note on the optional parameters without adding verbosity.

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 that an output schema exists (so return values are documented elsewhere) and the tool has only two optional parameters, the description covers the basic purpose. However, the complete lack of parameter documentation leaves a significant gap, making the description merely adequate.

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%, yet the description provides no explanation for the two optional parameters ('base_dir' and 'dotenv_path'). While both are optional with defaults null, the lack of any guidance means an agent cannot decide whether or how to set them. The description fails to add semantic value beyond the schema.

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 uses the specific verb 'Return' and clearly identifies the resource 'local private workboard target' with a condition 'when Gitea is unavailable.' This clearly distinguishes it from sibling tools like 'gitea_workboard_config' and 'local_workboard_init.'

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 states the condition for use (when Gitea is unavailable) implying that under normal circumstances one should use 'gitea_workboard_config.' It does not explicitly list alternatives or exclusions, but the context from sibling names provides clear guidance.

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