get_profile_stats

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

No annotations are provided, so the description carries the full burden. It states this is a 'get' operation, implying read-only behavior, but doesn't disclose any behavioral traits such as whether it requires an active profiling session, what format the statistics are returned in, or if there are any rate limits. This leaves significant gaps for a tool that likely interacts with profiling state.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose ('Get current profiling statistics'), making it easy to parse. Every word earns its place by conveying essential information without 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 complexity implied by profiling tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'profiling statistics' entail, how they relate to other tools like 'start_profiling', or what the return format is. For a tool in a debugging/profiling context with many siblings, this minimal description leaves too much unspecified.

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 input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly doesn't mention any. A baseline of 4 is appropriate as it avoids misleading parameter information.

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 'Get current profiling statistics' clearly states the action (get) and resource (profiling statistics), but it's vague about what specific statistics are retrieved and doesn't differentiate from sibling tools like 'get_coverage_report' or 'get_function_history' which also retrieve profiling-related data. It's better than a tautology but lacks specificity.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'get_coverage_report' and 'get_function_history' that might overlap in profiling contexts, there's no indication of when this tool is appropriate or what distinguishes it from other data-retrieval tools in the set.

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