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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates this is a read-only retrieval operation by saying 'get detailed information,' but it does not mention any permissions, error behavior (e.g., target not found), or side effects, which would be helpful for an agent to fully understand the tool's 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?

The description is a single, well-structured sentence that leads with the action and result ('Get detailed information') and then specifies the content. Every word adds value, with no wasted text or 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?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers the key return fields. However, it does not clarify the distinction from the closely related get_target_scores tool, which could be a source of agent confusion. Overall, it is mostly complete for a basic getter.

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?

The schema provides 100% coverage for the single parameter targetId with a basic description. The tool description adds no additional detail about the parameter (e.g., where to find the ID or its format), so it does not enhance what the schema already offers.

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?

The description clearly states 'Get detailed information about a specific target' with a specific verb and resource, and enumerates the types of details (status, uptime, fingerprint, composite scores). This distinguishes it from sibling tools like get_target_scores, which focuses on scores, and analyze_target, which implies deeper analysis.

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?

The description implies the tool is used when you need detailed information about a single target, but it does not explicitly state when to use this tool versus alternatives like get_target_scores or analyze_target, nor does it provide exclusions or prerequisites. Guidance is implicit rather than explicit.

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