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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the response payload shape (identity, access settings, appearance, knowledge, traits, data collection) and the readiness block with percent/missing keys/next steps, which tells the agent what it can act on next.

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 short sentences, front-loaded with the core verb and resource, followed by the payload contents and the one optional flag. The middle enumeration is long but earns its place by setting response expectations; no filler.

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?

An output schema exists, so the description need not explain returns, yet it helpfully previews the sections and the readiness block. For a two-parameter read tool with full annotation coverage, nothing an agent needs to invoke it correctly is missing.

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 100%, so both parameters are already documented. The description's mention of include_instructions adds only the behavioral framing (full instructions text) already captured by the schema's 'Include full instructions text' description and default note. Baseline 3 is correct.

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 ('Get a complete overview of an agent's configuration') and enumerates exactly what the overview contains, so the agent knows this is the read-side counterpart to the many gnosari_manage_* mutators. It stops short of naming any sibling, so the differentiation is inferable rather than explicit.

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?

No explicit when-to-use/when-not, but 'Set include_instructions=True for the full instructions text' implies the cheaper default path versus the full-text path, and the tool's position among manage_* siblings is deducible from the read-only framing. Guidance is implied, not stated.

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