get_component_context

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

Annotations only declare readOnlyHint=true, and the description adds real behavior: pagination via nextCursor until complete, the critical warning that JSON-fragment continuations must be concatenated in order then parsed, and that snapshot changes invalidate the cursor. It also warns that observed usage is static/advisory. It stops short of stating auth or rate-limit behavior.

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?

Purpose is front-loaded in the first sentence and every subsequent sentence carries a distinct operational fact with no padding. The telegraphic fragments are dense but occasionally abrupt, and the JSON-parsing caveat could be grouped more logically with the pagination note.

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 read-only inspection tool with no output schema, the description covers what the agent needs: what is returned (sections), how to retrieve it fully (cursor + fragment concatenation), and when the data goes stale (snapshot-changed). Missing only permission/error behavior.

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 0%, so the description carries the burden. It does map loosely to all four params: 'exact component ID' (id), 'selected snapshot' (snapshotId), the enumerated sections (sections), and 'nextCursor' (cursor). However, it gives no format constraints or defaults, leaving gaps the schema cannot fill.

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 ('Inspect an exact component ID in the selected snapshot') and enumerates the sections returned (API, guidance, relationships, source). It fails to explicitly distinguish itself from the sibling get_component, so the agent must infer the difference between 'exact ID' and the other component tools.

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?

Offers operational guidance (follow nextCursor, restart discovery after snapshot-changed) but never says when to call this versus siblings like get_component, get_component_catalog, or find_components. Usage is implied by the 'exact component ID in the selected snapshot' scoping rather than made explicit.

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