Configure account-wide settings

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

Description adds behavioral details beyond annotations: explains each gitMode option's behavior, planLimits usage and clearing, and that standard can be null to clear. Annotations indicate idempotent and non-destructive, which are consistent. Minor gap: no mention of permissions or side effects beyond what's described.

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?

Description is moderately concise, front-loading the main purpose. Each sentence adds value, though it could be slightly tighter. No redundancy.

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 configuration tool with no output schema, the description covers the main parameters and their use cases. It lacks information on return values or error states, but the tool is straightforward. Sibling tools are diverse but not directly competing.

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 only 33% (only defaultStandard has a description). The description compensates by explaining gitMode enum values and planLimits structure extensively. It adds meaning 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 clearly states the tool sets account-wide settings for FeatureBoard, and distinguishes it from per-project overrides via set_git_config. It specifies the exact resources (gitMode, planLimits, defaultStandard) and their behavior.

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?

Explicitly states the settings apply globally unless overridden per project, and advises asking the user about gitMode during onboarding. It provides context for when to use planLimits (after reading usage tab) and how to clear it.

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