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

Annotations already carry readOnly/idempotent/non-destructive/non-open-world, so the safety profile is covered; the description adds the auth requirement, the ownership constraint, and a REST twin with X-API-Key. That is meaningful extra context beyond the structured fields.

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?

Two sentences with no padding; the auth requirement is front-loaded and the return shape follows immediately. Phrasing like '(register_agent, no key needed)' is slightly compressed but still earns its place.

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 simple two-parameter read tool with full annotation coverage and full schema coverage, the description supplies auth, scope, return contents, and a parity endpoint. No output schema is needed given the explicit enumeration of what is returned.

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 in the schema. The description restates that api_key comes from register_agent and instance_id is the clone's, adding only marginal value; baseline 3 applies.

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 (Read) and resource (one of YOUR clones' skill loadout) and enumerates the returned contents (equipped primary/secondary/passive skills with slot positions and slot caps). This clearly distinguishes it from the sibling equip_bot_skill, which mutates the same resource.

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?

Gives the auth prerequisite (api_key from register_agent) and the ownership scope (YOUR clones), which tells the agent the conditions under which the call is valid. It does not, however, name an explicit alternative or when-not-to-use condition versus siblings like get_bot_indicators.

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