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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds value beyond them by disclosing the breadth of the read (full app configuration, not a slice) and positioning it as the diagnostic entry point, though it says nothing about response size or auth requirements.

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?

Three sentences, each earning its place: scope first, then usage priority plus alternatives, then the mutation counterpart. No filler and the most decision-relevant content is 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?

With no output schema, the description compensates by enumerating what the read returns, and it routes the agent to siblings for narrower slices. For a single-optional-param read tool this is complete enough to invoke correctly without further exploration.

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?

Only one optional parameter ('app') exists and schema description coverage is 100%, so the schema already explains the id and the omit-to-use-current-default behavior. The description adds no parameter-level detail, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('Read the full Bridge app configuration') and enumerates the concrete contents (name, URLs, login methods, redirect URIs, default role, plan/billing setup). It also explicitly separates itself from the narrower readers get_auth_config, get_environment_info, and get_setup_status.

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?

'Call this first ... before changing anything or diagnosing auth issues' gives an explicit trigger condition, and the description names three narrower alternatives with the condition that selects each. The write counterpart, update_app, is also named, closing the read/write loop.

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