Per-plugin breakdown

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

Discloses that excludeNative drops idle frames, adding behavioral context beyond schema. However, given no annotations, it does not cover other aspects like auth needs or rate limits, leaving transparency incomplete.

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 concise sentences front-load the primary purpose and a key behavioral detail, with no superfluous content.

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?

Describes the tool's action clearly but omits details about output format, ordering, and how topN limits results, which are important for an agent to fully understand usage.

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?

Adds meaning for excludeNative by explaining its effect, but does not describe topN or thread beyond what schema already provides. With 50% schema coverage, more parameter context would be beneficial.

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?

Description clearly states it groups self-time by plugin/mod source, referencing Spark's 'sources' view, and distinguishes itself from siblings like get_top_self_time by specifying the grouping dimension.

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?

Implies usage for identifying responsible plugins/mods but lacks explicit when-to-use or when-not-to-use guidance relative to alternatives like get_top_self_time.

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