plur_scopes_discover

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

Discloses default read-only behavior, the effect of register:true, and which scopes are auto-registered (shared vs personal). Annotations confirm idempotent but no contradictions. Missing details on auth requirements or response format but adequate.

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?

Five sentences with clear front-loading of purpose. Every sentence adds unique value without 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?

Well-described for a tool with no output schema and two optional params. Explains when to use, effect of params, and which scopes are handled. Could include response format but not required given no output schema.

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?

Adds significant meaning beyond schema: explains default behavior of url parameter and the effect of register parameter. Schema coverage is 100% but description enriches understanding.

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?

Description clearly states the tool discovers authorized scopes and differences from local registration. It distinguishes from siblings by specifying usage for multiple team scopes.

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?

Provides explicit usage context: 'when you have access to multiple team scopes on one server.' Explains when to use register:true but does not explicitly state when not to use.

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